Nectarine
Site Development » HTTPS only?
Pages:
1
| Author | Thread |
|---|---|
 mirrorbirdsymptomless coma 383 Posts #1346 (3 years, 8 months ago) |
Should we think about changing the site to support HTTPS only, and deprecate/remove unsecured HTTP? This seems to be quite a common practice now. Redirecting HTTP to HTTPS URLs can be achieved with a line or two in the .htaccess file.
|
| Quote | |
|
mirrorbird symptomless coma 383 Posts #1376 (3 years, 7 months ago) |
Coincidentally, it seems that the Nectaplayer (online player widget) has just stopped working in the latest Chrome (85), and I believe it's related to this: https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html It shows an error along these lines: Mixed Content: '/demovibes/play/' was loaded over HTTPS, but requested an insecure element ':8000/nectarine'. This request was automatically upgraded to HTTPS. |
| Quote |
Pages:
1
Post a Reply
Please log in to post a reply.