Now Chrome has decided to place this warning on all HTTP pages going forward. In addition, the warning is displayed on all HTTP pages in incognito mode regardless of whether they contained an input field or not.įirefox also warns users when they attempt to fill an insecure login form. In an effort to drive users away from insecure sites, browsers have been shaming websites served insecurely in certain contexts.Ĭhrome 56 started that trend by marking pages with sensitive login fields as “Not secure” while Chrome 62 extended this warning to all HTTP pages that contained any type of input field. If you’re not convinced, read to get the full picture of why every website should be served securely.Īnd if you still don’t get it, then life is about to get a lot harder for you.
I’ve written about the value of HTTPS previously, but just to reiterate: This is the strongest nudge yet to drive the web towards encryption by default and has been a long time coming.Īlthough there is a ton of evidence that speaks to why everyone should hop on the HTTPS bandwagon, a lot of people still don’t see the value in serving their sites securely.
The planned change in the Chrome address bar Last week, Google announced that Chrome 68, arriving in July, will mark all HTTP pages as “Not secure”. By Ayo Isaiah How to add HTTPS to your website for free in 10 minutes, and why you need to do this now more than ever Photo by Daniel Corneschi on Unsplash
0 kommentar(er)
