The green “Secure” text will no longer be present starting in Chrome 69. To avoid this you will need to obtain an SSL certificate for your website and deploy HTTPS-ideally to every page.Ĭhrome 68 adds a warning for HTTP pages, and Chrome 69 (expected to release in September) will remove a familiar indicator for HTTPS pages. This will be a major change for websites and pages still using HTTP as they will now receive prominent warnings making users aware of the insecurity of the HTTP protocol. On all HTTP pages, Chrome 68 displays a warning reading “Not Secure” to the left of the URL in the address bar. The biggest change so far has come in Chrome 68 (released July 24th, 2018), which has become the first version of any major browser to warn users about all HTTP pages. Now that the majority of the internet is secure, expect to see a shift from ‘positive’ indicators that promote websites with HTTPS, to ‘negative’ indicators that will warn about websites still on unsecure HTTP (see an example of this warning further down). Note that similar changes in other major browsers are not far behind either. As Chrome increases warnings for HTTP pages, and further restricts their functionality, having an unsecure site will become a liability for your brand’s image, your conversion rates, and a headache for your customer service team. Websites and organizations that have yet to deploy HTTPS-or are still working with partial deployments of HTTPS (for example, only protecting login/checkout pages)-will want to play close attention. This post will help you keep track of what these indicators look like today, and to plan for what they will be in the future. The UI that was needed in 2014, when the majority of pages loaded via Chrome were performed over HTTP, is not the same UI we need now-where 75% of pages are now accessed over HTTPS. The internet has undergone an HTTPS renaissance over the last 10 years since it became obvious that troves of sensitive data were being sent around the world and that threats to, theft of, and surveillance of that data was growing quickly.Ĭhrome’s security UI has evolved both in response to the increased adoption of HTTPS, and to further encourage it.Īll these changes may feel confusing, but a slow step-by-step approach has allowed Chrome to ease users in to the evolving internet landscape. If you are a regular user of Chrome or work in web development/IT, you’ve likely noticed frequent changes to the browser’s ‘security UI’-the icons and indicators that tell users if the page they are visiting is secure.
0 kommentar(er)
