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.
The original home of HTML tutorials. HTMLGoodies is a website dedicated to publishing tutorials that cover every aspect of being a web developer. We cover programming and web development tutorials on languages and technologies such as HTML, JavaScript, and CSS. In addition, our articles cover web frameworks like Angular and React.JS, as well as popular Content Management Systems (CMS) that include WordPress, Drupal, and Joomla. Website development platforms like Shopify, Squarespace, and Wix are also featured. Topics related to solid web design and Internet Marketing also find a home on HTMLGoodies, as we discuss UX/UI Design, Search Engine Optimization (SEO), and web dev best practices.
Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.
