3 ms·
Your 20y old site gave me https errors when I tried to click it, fyi
by bobthepanda 8mo ago
Your 20y old site gave me https errors when I tried to click it, fyi
- q3k 8mo agoDon't access it over https then? The link is http.
- 01HNNWZ0MV43FF 8mo agoWorks fine on my end. The HTTPS URL gives a 301 permanent redirect to HTTP, and then I ordered some boner pills and put my social security number to confirm.
- LoganDark 8mo agoDon't modern browsers automatically redirect http to https?
- qu4z-2 8mo agoThen use a non-buggy browser...
- Gigachad 8mo agoNo they don't. I tried Chrome, Firefox, and Safari. None of them attempted to redirect. They just show a "not secure" warning in the URL bar. The redirect only happens when it's configured on the web server, set in HSTS, or on a TLD that enforces HTTPS. None of these apply to this website.
- LoganDark 8mo agoApparently it's not on by default, but all of my browsers do and also warn me whenever a site does not support HTTPS (and require me to explicitly click through to the unencrypted connection).
- kmeisthax 8mo agoNot unless the site sends the CSP header to tell it to upgrade to https: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/upgrade-insecure-requests https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/... A client side option to force https might still be useful though. But I can imagine at least some enterprise webapp that would die horribly if you tried this.
- zoobab 8mo agoWikidot still does HTTP by default, they should at least upgrade to both HTTP+HTTPS, i asked the support never got any reply.