• Please review our updated Terms and Rules here

Video hosting

Well if you use relative links that will take care of itself.
 
It depends.

If you want to support both HTTP and HTTPS, then use relative links when popping around through pages on your own site. That way the user can choose how they want to get to your site at the beginning (HTTP or HTTPS), and then any link that the follow is relative to the original link.

If you are leaving your site to another site, you can try to default to HTTP. If they want to force HTTPS they'll take care of that.

On my site I only force HTTPS on the PCjr web forum; otherwise I let the user access the static content using HTTP or HTTPS. This is friendlier to older computers.
 
Hmm, turns out that I never put much thought into relative vs non-relative links with my *.htm being a mixture of both. For the sake of tidiness if nothing else I have now gone relative exclusively. I decided in the end to just force https. I got project document *.pdf files out there which just give my site domain as a www. If not forcing/redirecting to https you're then relying on someone trying to access your site by typing in the URL being knowledgeable enough to try typing https://www if their browser throws up a security warning after trying just www.

This security stuff is just going to get enforced more and more in the future. After a recent update Firefox now refuses to let me log into my solar inverter.
 
Back
Top