View Single Post
Old 18th May 2021, 03:59   #4
HG2S
Junior Member
 
Join Date: Sep 2020
Posts: 16
Frankly, I think you want to move to HTTPS as soon as you can. In time HTTP will not be supported and you'll be forced to move to HTTPS in a under duress.

You might consider not forcing the HTTPS connection, at least initially. That is, do not enable a forced redirect to HTTPS on your site. Offer both HTTP and HTTPS and let the client (or coder) choose which connection to make.

As to mixing HTTP and HTTPS on the same page, it can work with older browsers but appears to be waning. I wouldn't guess it is long for this world. Take a look at what Mozilla has to say about it:

Quote:
If your website delivers HTTPS pages, all active mixed content delivered via HTTP on this pages will be blocked by default. Consequently, your website may appear broken to users (if iframes or plugins don't load, etc.). Passive mixed content is displayed by default, but users can set a preference to block this type of content, as well.
If you need help with a streaming app that does HTTPS you might consider talking to the guys at RadioRethink. They specialize in helping community and public radio stations connect with their listeners.
HG2S is offline   Reply With Quote