Beginning this October, Google Chrome will begin warning users that any Web pages that accept user input via the HTTP protocol are “not secure.” Web developers can make sure that their site visitors don’t receive the warning by using the HTTPS protocol instead. “Passwords and credit cards are not the only types of data that should be private,” blogged Emily Schechter, a member of Google’s Chrome security team. “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.”
At the same time, Chrome also begin displaying an identical security warning for any HTTP Web pages that users visit while in Incognito mode.
Google has been pushing Web developers to use HTTPS instead of HTTP for some time.
