4 ms·
Ask HN: Why did Google just push a chrome update removing the “Not Secure” flag?
I just updated my chrome (Windows Stable) branch to version 57.0.2987.98. chrome:// pages have their own flag now, HTTPS pages still have the "Secure" flag but HTTP pages just have the unlocked icon. Does anyone know why Google did this? It seems unlike them to rollback a change like this.
- detaro 10y agoIs the "not secure" gone from all pages? I thought it was only supposed to show on pages with password fields?
- chipperyman573 10y agoI was under the impression it used to be on all pages. I just checked http://http-password.badssl.com/ http://http-password.badssl.com/ and it still showed up there, maybe you're right.
- joshschreuder 10y agoLooks like it's only for HTTP pages with credit card or password inputs in 56: https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn https://developers.google.com/web/updates/2016/10/avoid-not-... Did they remove it for those cases too?
- skyisblue 10y agoThe http site you were viewing may have just removed a login form from their menu, which would have removed the not secure label from the browser.