4 ms·
I'm curious, why the https? Muscle memory?
by Whitespace 13y ago
I'm curious, why the https? Muscle memory?
- dfc 13y agoI bet the answer is HTTPS Everywhere. The only bad thing about it is the mixed content blocking, but I still think everyone should use it. There was a link to schneier's blog here recently and a few people mentioned that his cert was expired. I am willing to be that everyone who saw the cert warning were httpseverywhere users. https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere
- pondababa 13y agoPerhaps he's using HTTPS Everywhere.
- frossie 13y agoI didn't post it, but I assume s/he was cutting and pasting from their URL bar, and they use HTTPS Everywhere or similar to encourage their browser to always prefer HTTPS connections (which xkcd provides, but to my ongoing annoyance, Amazon does not). https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere One could argue this should be a built-in option these days....
- graue 13y agoUnfortunately, xkcd (along with NYTimes and probably others) link to CSS/JS resources at http:// http:// URLs, which defeats the security of HTTPS. The next version of Firefox will block mixed content in these cases, and being on the alpha channel, I've had to disable HTTPS Everywhere for these sites.