Google Chrome will request HTTPS links by default
Google Chrome has recently made many adjustments in terms of security, although some adjustments have serious negative effects.
However, the company is still preparing new adjustments, including requesting HTTPS encrypted secure connections by default to improve security while also improving performance.
This default request for HTTPS encrypted connections is currently being tested, and it is expected that it will be pushed to the stable channel for all users soon after the test is completed.
Normally, when you enter google.com in the address bar, the address recognized by the browser is http://google.com/, and its prefix is HTTP plaintext protocol.
Only when the user enters https://google.com is an encrypted connection requested, and the browser will also redirect the transmission protocol by default.
For example, Google uses encrypted secure connections by default, so even when requesting google.com, it first jumps from the HTTP plaintext protocol to the HTTPS encryption protocol.
So this situation is not only not safe enough, but also needs to actually increase the actual request and server overhead through the jump, so Google is ready to improve this situation.
Google named this improvement as the upgraded HTTPS navigation, which will be used by default in subsequent versions of Google Chrome to improve security performance.
Google said that after testing, this navigation method can not only improve security but also reduce server overhead. Overall, it is a very good security improvement.
However, this security improvement is not fully usable at least for now, because there are still many websites that use plaintext protocol transmission that cannot be encrypted.
Therefore, after Google Chrome requests an encrypted connection, there will be a timeout period. If the encryption protocol does not respond within the specified time, it will request a plaintext connection again.