Google continues to improve Chrome by testing a feature that makes it open the HTTPS pages of the sites visited as a priority. The protocol, more secure than its cousin HTTP, is currently loaded second, which can slow down browsing. The device is not yet available, because it could “break” the sites which are still in HTTP.
Safety is a major issue web browsing, and Google got it right. After correcting the crash bugs and excessive RAM usage, the firm is looking into a new feature of Chrome which may soon arrive. Currently, when a page with the HTTPS protocol is visited, the browser load the HTTP version first before displaying the secure version. Google wants Chrome to remove the first step to directly load the HTTPS version.
This feature called “Upgraded HTTPS navigations” (“Enhanced HTTPS browsing”) will take place in the Omnibox, namely the address bar. The latter has already been the subject of several optimizations over time, especially in terms of its readability by removing the protocol from the URL. Once deployed, the solution will also allow autocompletion to take into account the HTTPS version of the desired page. Note that this change could apply to Edge, the two browsers sharing the same kernel: if Chrome improves, Edge too!
Google emphasizes security for Chrome
As a reminder, the HTTPS protocol is in a way an improved version of HTTP by implementing a secure connection between the visited site and the browser. The stake is therefore twofold according to Google: on the one hand, the firm declares that “The web is increasingly adopting HTTPS”, which shows a growing attention to safety; on the other hand, the developers claim that the device will allow Chrome to load pages faster concerned.
Read also: Chrome 87 is faster, more efficient, more economical, here are the new features of the update
These also specify that the browser “Will search for enhanced HTTPS versions for a few seconds before canceling the upload if necessary, so as not to wait indefinitely for an HTTPS page that does not exist”. However, although it is a “Minor improvement” according to its creators, they admit that it “Not ready for use”. Indeed, Chrome being for the moment unable to remember which URLs direct to an HTTP page, the functionality could break some sites having remained on the unsecured protocol.
Source: Windows Latest