Chrome goes Https Default

Chrome browser version 90 will arrives in mid-April, initial website visits will default to a secure HTTPS connection in the event the user has failed to specify a preferred URI scheme. when a user types “www.example.com” into Chrome’s omnibox, without either an “http://” or “https:// prefix,” Chrome chooses “http://.” The same is true in other browsers like Brave, Edge, Mozilla, and Safari.

This made sense in the past when most websites had not implemented support for HTTPS. 2 years back the majority of websites redirected traffic to HTTPS. But these days, most of the web pages loaded rely on secure transport in which most of them are Https

Previously, only websites that declared they should be loaded securely with an entry on an HTTP Strict Transport Security (HSTS) preload list – supported in multiple browsers – got HTTPS automatically.

Chrome 90 will make HTTPS the default for first time website visits where no transport has been declared. Beyond the security and privacy benefits, this will improve performance since the delay incurred by redirection from an http:// endpoint to an https:// endpoint will no longer happen.