[TazeTSchnitzel]

A little OT, but using HTTPS Everywhere has shown me how badly SSL is configured on many sites. Default certs for root domain being used on subdomains, scripts and styles loaded over HTTP (and hence blocked by Chrome - by far the most common and most annoying), HTTPS port listened on but no site served, default certs for completely unrelated sites showing up, etc.

[notatoad]

Easy solution: stop using HTTPS Everywhere to force HTTPS in cases where the admins aren't supporting it. The admins haven't configured it badly, they've configured it for the cases they want to support. Using an extension to force non-standard behaviour breaks things.

[TazeTSchnitzel]

"Force non-standard behaviour"?

If I connect using a protocol to a site, it should work! If said protocol is poorly configured, it shouldn't be available!