Tag Info

New answers tagged

0

All those 3 domains are completely independent from each other (even if they are different virtual hosts in the same apache server). A protocol-relative URL just means "use the same protocol as the current page's". So, yes, you need to configure https certificates for all those domains. Otherwise the browser may produce a warning saying that some resources ...


3

The problem is because you have some of the images hard-coded to load through http protocol on your index page. You should change the links to be protocol-agnostic by using //, e.g.: <img src="http://example.com/image.png"> Change with: <img src="//example.com/image.png"> These links will make content load through https if site is also ...


0

How to test it? Just go to https://yoursite.com/, if it pulls up, it works!


2

If you see a totally different website, and your site is on shared hosting, it may be the case that your hoster has a configuration problem. This was the case in a similar question: "https://" refers to random site, "http://" is broken, but "http://www" works Check if your and the other site are hosted by the same provider ...


1

As you say you are directed to a compromising website, I would check that your site hasnt been hacked in some way with a unwanted redirection to the said website.


5

No, you do not need a separate registration. http:// or https:// are just protocol specifiers. The name will resolve to the same host. However, once you're on the hosted machine, the web server determines what to display. Often, HTTP (port 80) and HTTPS (port 443) can be routed to different pages. This should be configurable by the website admin/tools. In ...


1

The best .htaccess code which I am able to give you to do the redirection is as following: # This allows you to redirect your entire website Redirect 301 / http://example.com/ You will have to modify the example as you add it into your .htaccess file.


1

HTTPS can achieve two things: Authentication. Making sure that you are communicating with the real domain owner. Encryption. Making sure that only this domain owner and you can read the communication. Probably everyone agrees that HTTPS should be mandatory when transmitting secrets (like passwords, banking data etc.). But there are several other cases ...


1

With me helping with the back-end system for a web hosting company, we strive to make sure our customers personal data is secured by SSL and we do encrypt their name, address, and phone numbers to just make sure if there is any data breaches, there should be minimal damage as possible. Trust is one thing when it comes to having loyal clients. As for your ...


1

You'll want to use SSL for any pages in the checkout process, for sure. Encrypting address data in your own database is optional. If someone were able to access your database, they'd likely be able to get your encryption key also, so that would provide little defense. Also name and address are not nearly as sensitive of information as credit card data.



Top 50 recent answers are included