The one in particular that we’d like to highlight is their shift to making HTTPS the default protocol when loading websites for most users. In the Chromium Project blog’s March 23 update, Google announced many updates that they’ll be rolling out as part of their Chrome 90 update. But when and why are they implementing this update? Is Chrome forcing HTTPS? And what does this change mean for your website?
In reality, this is a logical move considering that the latest data from Google’s Transparency Report shows that 95% of sites across Google already use encryption to protect their traffic. Their latest browser update, version 90, is expected to use HTTPS by default when a user types in a website address without specifying the protocol. And Google, recognizing that many browser users don’t type in complete URLs when accessing websites, decided to bridge the gap between user experience and security this year. It’s no secret that using HTTPS to serve up your website is faster and more secure than using the default HTTP protocol.
For example, Chrome will load “” when a user types “.” (And if the HTTPS fails because a site lacks SSL/TLS, it’ll revert to using HTTP.) In Beyond Hashed Out, Industry Lowdown Google Chrome version 90 will default to HTTPS for incomplete URLS.
0 kommentar(er)
