Dec. 29 (Portaltic/EP) –
the web browser Google Chrome is testing a function to increase user protection what blocks all potentially unsafe HTTP downloadsan action that it will perform even if they come from environments initially insurance.
Currently, websites frequently use the HTTPS protocola secure encryption that prevents that other users can intercept confidential information that is transferred between the client and the web server over the internet.
Along with this security protocol, the HTTP information transmission protocol, which follows a request-response scheme between the web server and the client that makes the data transmission request. Unlike the previous one, HTTP is not protected against the intervention of third parties.
However, it should be noted that although it is true that the HTTPS format gives users greater confidence, the ‘S’ of a certain web page does not guarantee that it is protected from all threats.
As Google reflects in its Google Chrome Help section, there is a way to manage browser security through HTTPS mode. When users turn on this protocol in the first instance, Chrome tries to load all websites over HTTPS and displays a warning before visiting a site that doesn’t support this protocol.
Along these lines, as has been warned 9to5Googlethe company is testing a new feature what blocks all insecure HTTP downloads, even from secure sites. This means that it will not allow downloads from HTTPS links that redirect to HTTP servers.
It is therefore a question of blocking of so-called mixed downloads what, as explained by Google itself in the Chromium ‘bugs’ forum, they are “unsafe downloads that start from safe contexts”, which is why it has implemented warnings and blocks of unsafe downloads.
At the moment, this new option forms part of a Chrome ‘flag’, that is, from an experimental phase, so it is in a trial period. However, from the aforementioned medium they point out that it is likely that, later on, this feature will be integrated into the section ‘Always use secure connections’.
Likewise, 9to5Google indicates that it is not likely that this functionality will be extended to more testers until the release of Chrome 111, scheduled for March 2023. The global release, instead, would take place later.