3 ms·
Not by default. When leaving chrome://flags/#mark-non-secure-as on "default", even in Chrome 55, non-secure sites are just neutral and don't have any specific n
by Ambroos 10y ago
Not by default. When leaving chrome://flags/#mark-non-secure-as on "default", even in Chrome 55, non-secure sites are just neutral and don't have any specific non-secure indication.
This flag has been available for a long time, since at least December 2014. The visual has been updated slightly in 54 or 55 (secure sites do now get the "Secure" badge instead of just a green lock). There is no change in default behaviour though. From time to time Canary changes the default to mark non-secure sites as non-secure, but it's always been rolled back very quickly. It's coming, but probably not very soon.
A story like this makes tech news from time to time. In January this year a lot of sites posted about it, and when the flag was introduced late 2014 many of them did too. As long as there's no announcement from Google or the Chromium team (and there would be), nothing is changing.
- nailer 10y agoYou're correct: this is hidden behind a flag that's not currently enabled. The behavior in Chrome 55 (and also 53, the current stable) is the (i) indicator. Clicking on it tells you the website "isn't private": https://certsimple.com/images/blog/american-apparel-insecure.png https://certsimple.com/images/blog/american-apparel-insecure... However Google do intend to mark HTTP as non secure: for indications of future plans, best place to go is directly to the source: see 'Marking HTTP As Non-Secure' https://www.chromium.org/Home/chromium-security/marking-http-as-non-secure https://www.chromium.org/Home/chromium-security/marking-http... Note: I work at CertSimple.
- theandrewbailey 10y agoHonestly, I've been waiting for the "http = scary red error" change to happen for a while, so I can encourage my company's e-commerce clients to go 100% HTTPS only.