Google Chrome will soon be running an experiment that will automatically attempt to connect to the HTTPS versions of website URLs that you enter in the address bar instead of the insecure HTTP version.
HTTPS has not been secure for years It comes to the point where Chrome does not display “Safe” on an HTTPS website, but rather “Unsecure” on a standard HTTP website.
With HTTPS is becoming an effective standard. Since then, parts of the URL have been hidden in the Google Chrome address bar that is not relevant to the average person surfing the Internet – for example, www., Http: // and https: //. This lack of distinction has resulted in an increase in the number of people who simply type a URL like “9to5google.com” in their address bar and press Enter.
As you’d expect, Chrome can do more than figure out where you are, but it may not be what you might expect. The first time you navigate to a specific website in this way, Chrome tries to test the unsafe version of the URL (for example, http://9to5google.com). Most websites with a secure version will redirect you to the secure https: // URL. Chrome will then record whether this HTTPS redirect took place or not and will remember for the next time to jump straight to https: // URL.
In the next few months, it looks like Google has plans to reverse the bar’s priorities. Chrome’s address, according to a new flag added to chrome: // flags, as well as an associated message on issue tracking.
From what we can see in the description and associated code, Google Chrome will first try to connect to the HTTPS version of any URL you type If the site does not offer HTTPS – such as a test site like NeverSSL – Chrome will give up after 3 seconds or 10 seconds and connect to the site over HTTP instead.
Overall, this seems like a change that thanks to efforts like Let’s Encrypt that make HTTPS simple, even for developers Most inexperienced webs, there really is no reason why browsers like Chrome shouldn’t try to connect over HTTPS first.
The Chromium code, probably won’t appear in Chrome stable until version 89 or 90 which is expected in March and April respectively, even then it will probably take a few more months before Google Chrome’s address bar does. defaults to https: // URLs without needing to use the Chrome flag above.