Today, Chrome Takes Another Step Forward in Addressing the Design Flaw That is an Unencrypted Web
In July 2018, Google's Chrome browser began flagging all non-secure connections as "not secure." This move is part of a broader effort to drive site owners towards a more secure web by addressing the design flaws of the original unencrypted web. The push for HTTPS has seen significant growth in recent years, with many large websites adopting it by default. Despite this progress, some website owners still question the necessity of secure connections for sites without the need for confidentiality. However, as Google continues to move towards a "secure by default" web, the adoption of HTTPS is likely to become even more widespread.
Company
Cloudflare
Date published
July 24, 2018
Author(s)
Troy Hunt (Guest Blogger)
Word count
1571
Hacker News points
None found.
Language
English