Our plan
to label HTTP sites as non-secure is taking place in gradual , based on increasingly broad criteria. Since the change in Chrome 56, there has been a 23% reduction in the fraction of navigations to HTTP pages with password or credit card forms on desktop, and we’re ready to take the next steps.

Passwords and credit cards are not the only types of data that should be private. Any type of data that users type into websites should not be accessible to others on the network, so starting in version 62 Chrome will show the “Not secure” warning when users type data into HTTP sites.

- dmaHJpLKiq9RfhyN81jd9KQyohOAJh1UW5Fv978fiWTcl98u4rMoJy0CaOmiFi1NYE7zCoAsG 1CW6O9PL8ytpRC8Lzz 8dtd7NC4IOM5eG6AfLEorCpV13CrNnMVdwzSLTKZOn1 - Next Steps Toward More Connection Security

Treatment of HTTP pages with user-entered data in Chrome 62

When users browse Chrome with Incognito mode, they likely have increased expectations of privacy. However, HTTP browsing is not private to others on the network, so in version 62 Chrome will also warn users when visiting an HTTP page in Incognito mode.

Eventually, we plan to show the “Not secure” warning for all HTTP pages, even outside Incognito mode. We will publish updates as we approach future releases, but don’t wait to get started moving to HTTPS! HTTPS is easier and cheaper than ever before, and it enables both the best performance the web offers and powerful new features that are too sensitive for HTTP. Check out our set-up guides to get started.

Source link


Please enter your comment!
Please enter your name here