The developers of Google Chrome announced that the browser will now forcefully add the prefix HTTPS to the Internet addresses of the sites.
Over the years, Google engineers have been among the most outspoken proponents of better browser security, along with the developers of Firefox and Tor.For a long time, one of the key issues of interest to Chrome developers has been the promotion of the use of HTTPS both within browsers and among site owners. The next step towards ubiquitous HTTPS is that recently Chrome automatically tries to switch from HTTP to HTTPS if HTTPS is available.
Although about 82% of all sites are already running HTTPS, the transition to HTTPS globally is far from complete. Therefore, a new feature will appear in Chrome 90, scheduled for release in mid-April this year.
The change will affect the Chrome Omnibox (as Google calls the browser address bar). In current versions, when a user enters a link into the Omnibox, Chrome loads the entered link regardless of the protocol used. Now, if the user forgets to write HTTP or HTTPS, Chrome will automatically prepend the text “http://” and try to load the site. For example, domain.com will become http://domain.com.
This will change with the release of Chrome 90. Starting from this version, Omnibox will load all domains via HTTPS, automatically substituting the appropriate “https://” prefix.
Users can already test the new mechanism in Chrome Canary. To do this, you need to enable the function in chrome://flags/#omnibox-default-typed-navigations-to-https.
Let me remind you that I also talked about the fact that Soon, Chrome will stop using all the RAM on PCs and smartphones.
