Chrome 68 Released: HTTP Sites Marked as “Not Secure”
As somebody on the dev build train normally I&#x27;ve seen this change for quite a while now and my brain quickly stopped processing the warning on HTTP only sites.<p>I hope that flipping the switch now will cause enough of the remaining non-https sites to start looking into switching before Chrome feels the need to start adding &quot;more prominent&quot; warnings (for example using a modal dialog).<p>I agree that, yes, in general, we should all be using HTTPS on the internet, but non-secured HTTP still makes sense for example during development or for home routers and printers where traffic encryption is less important compared to the initial UX (my parents could probably set up a home router on their own if it&#x27;s using non-encrypted HTTP but they would be totally unable to proceed if it&#x27;s using a self-signed cert).