Google Chrome users have many options for loading web pages and web applications into the browser.
They can click on links, use bookmarks, or type the URL directly into the address bar to open websites.
If a user enters a complete domain containing a protocol, it opens as it is, but what happens when the user does not specify the protocol? When you type iguru.gr and press Enter, does Chrome load the page directly with HTTPS or try HTTP first?
It turns out that Chrome tests the HTTP version by defaultchoice. This of course made sense at one point as most websites didn't use HTTPS. Today things are different.
Google plans to introduce a new feature in the Chrome browser to make HTTPS the default.
A recent comment at Chromium, confirms the company plan.
Default typed omnibox navigations to HTTPS: Initial implementation
Presently, when a user types a domain name in the omnibox such as "example.com", Chrome navigates to the HTTP version of the site (http://example.com). However, the web is increasingly moving towards HTTPS, and we now want to optimize omnibox navigations and first-load performance for HTTPS, rather than HTTP.
Google will modify the code, so that the main box and autocomplete codes use the HTTPS protocol by default. Google calls it “upgraded HTTPS navigations”.
Chrome will use HTTP if HTTPS is not supported. SSL errors will be ignored by Chrome if the HTTPS connection does not work as long as it was part of an HTTPS upgrade.
the current application not yet ready for general use according to Google. One drawback is that it waits for the HTTPS connection to fully load or fail before trying HTTP. Future versions will automatically abort loading to test HTTP connections.
The feature will first be implemented in Chromium and then integrated into other Chromium-based browsers (Microsoft Edge, Opera or Brave).
