Google’s Plan For Chrome To Clamp Down On Unsecured HTTP Connections Starts In January 2017

Google’s inexorable march towards “a more secure web” continues, with the internet giant recently posting an update regarding the next steps it will take with Chrome to flag “non-secure” websites. 2017 looks like the year things will get serious, with sites featuring data-sensitive form fields and no HTTPS support in the crosshairs.

The start of 2017 will mark the first of many changes to Chrome that will “eventually” classify HTTPS-less sites as “non-secure” regardless of their content, according to Emily Schechter of the Chrome Security Team.

Chrome 56, which is slated for a January release, will “mark HTTP sites that transmit passwords or credit cards as non-secure”, writes Schechter.

Changes such as this will be added incrementally, until finally, “all HTTP pages [will be marked] as non-secure” and you’ll see the lovely red text and icon above.

It’s sufficient to say if you haven’t already sorted out a migration plan, certificates, etc., best to get onto it before the end of the year, especially if your sites feature an ecommerce element.

Moving towards a more secure web [Google, via gHacks]

The Cheapest NBN 50 Plans

Here are the cheapest plans available for Australia’s most popular NBN speed tier.

At Lifehacker, we independently select and write about stuff we love and think you'll like too. We have affiliate and advertising partnerships, which means we may collect a share of sales or other compensation from the links on this page. BTW – prices are accurate and items in stock at the time of posting.


3 responses to “Google’s Plan For Chrome To Clamp Down On Unsecured HTTP Connections Starts In January 2017”