Hot answers tagged

12

Stack Exchange has a lot of mixed content which is blocked by modern browsers' Mixed Content Blocker implementations. Ref Firefox, Chrome, IE/Edge, W3C editor's draft. As pointed out in question comments, Nick Craver tweeted recently that the conversion work is close to being done. He also has a much older post detailing why turning on HTTPS is so ...


3

The name in the certificate does not match the host name to use. The certificate is valid for lots of different names and includes wildcards such as *.meta.stackexchange.com (which would match against unix.meta.stackexchange.com) but no name which matches against meta.unix.stackexchange.com. Note that the included *.stackexchange.com will not match because a ...


1

Doesn't HTTPS Everywhere have a whitelist/blacklist facility where you can disable it on certain sites? I found these directions on making your own rulesets: HTTPS Everywhere Rulesets. Though I agree with you it would be best if you didn't need to workaround this. I think your request is apt.


Only top voted, non community-wiki answers of a minimum length are eligible