That's because HTTPS Everywhere doesn't blindly attempt HTTPS connections, it redirects based on a massive set of rules. That's also how it accounts for more co

That's because HTTPS Everywhere doesn't blindly attempt HTTPS connections, it redirects based on a massive set of rules. That's also how it accounts for more complex changes than just the protocol portion of the URL, like adding an encrypyted. or ssl. subdomain. You can see all the rulesets here: https://gitweb.torproject.org/https-everywhere.git/tree/src/chrome/content/rules https://gitweb.torproject.org/https-everywhere.git/tree/src/...