Comment on Chromium Blog: Towards HTTPS by default
LordXenu@artemis.camp 1 year ago
Pushing traffic to https isn’t the worst thing. My ask would be to have a toggle to disable due to local development or server deployments where http/port 80 is the only choice.
lily@shinobu.cloud 1 year ago
It does specifically say “defaulting to https:// if the site supports it”, so I think specifying http will still work if the site doesn’t actually support https.
Valmond@lemmy.mindoki.com 1 year ago
Got a message back from Https, let’s switch!
The message:
“Internal nginx routing error.”
dust_accelerator@discuss.tchncs.de 1 year ago
No testing a server side http-to-https upgrade/redirect without reconfiguring your browser. This seems like an unnecessary and bad idea.
This could be easily done better by promoting such server-side configurations as a default.
I mean, why should the browser attempt to correct inappropriately configured servers? Shouldn’t they rather be making PRs to NGINX/Apache/CAs or whatever?