When we open a web page in the browser, in many cases they work both in HTTP and HTTPS . A few years ago the first option was the most common, since not many sites were encrypted. Today the opposite is true. When putting an address in Chrome , without specifying whether it is HTTP or HTTPS, so far initially tested the first. This is going to change.
Chrome will first test HTTPS when putting a web
We have different options to enter any website . We can get there through a Google search, click on any link, access from bookmarks … But the most basic and simple thing is to put the URL in the address bar and enter. That is the same in any browser we use.
Now, as we know today, it is not necessary to have to put http and www before the domain name . At least not in most modern browsers that we use. This means that simply putting redeszone.net will take us to the web. Google Chrome, at least so far, will initially test HTTP in these cases.
Chrome will first test HTTPS when a user enters a domain without specifying the protocol. Nowadays this makes more sense than trying HTTP before, since as we have said there are many more sites that are adapted to the encrypted protocol. This popular browser, which is currently the most used worldwide, will include new functionality so that opening sites in HTTPS is the default.
Improve initial charge
Until now, Google Chrome tried HTTP first when we put a web address without specifying the protocol. From Chrome they indicate that what they are looking for now when they first try HTTPS is to optimize the performance of the initial load.
What if a page is not HTTPS? It is true that most websites are adapted to this protocol, but there are still some that are not. In these cases Chrome will use HTTP, but it would already be a second option.
Therefore, first of all what the browser is going to do is try to load the HTTPS version of a website. If that protocol is available, you don’t have to do anything else. In case it is not it is when it would resort to testing via HTTP, the unencrypted protocol.
Feature available in Chromium browsers
It should be noted that this new feature will be available for Chromium . This means that it will not only affect Chrome, although it is the most used browser, but we can also see it in Vivaldi, Microsoft Edge, Opera or Brave.
One thing users may wonder is whether this will improve performance. Although they do not indicate anything, it is to be expected that the improvement will be practically imperceptible. It could happen that, at least initially, HTTP sites take a little longer to load, since it would become the second option that the browser tests.
Ultimately, Google Chrome and other Chromium-based browsers are going to start testing HTTPS first when we put an address in the browser without specifying the protocol. We leave you an article where we explain how the HTTPS protocol works.
