Unfortunately, that would break a large number of sites out there. Some serve different content (as in: not what the visitor would be expecting) on HTTPS, many

Unfortunately, that would break a large number of sites out there. Some serve different content (as in: not what the visitor would be expecting) on HTTPS, many would have mixed content warnings, etc. Just take a look at the ruleset used by the HTTPS Everywhere extension[1] to get a sense for how much of the web would break in weird ways if browsers decided to do this today. This'll happen eventually, but with 50% of page loads using HTTPS, we're not quite there yet. [1]: https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules https://github.com/EFForg/https-everywhere/tree/master/src/c...