If your site overlays an HTTPS login frame over HTTP pages. Warning: It is NOT sufficient to place an HTTPS iframe inside a HTTP page the top-level page itself must be HTTPS as well.
This means that the top-level page must be HTTPS and, if the input is in an iframe, that iframe must also be served over HTTPS. To ensure that the Not Secure warning is not displayed for your pages, you must ensure that all forms containing elements and any inputs detected as credit card fields are present only on secure origins. When the Not Secure state is shown, the DevTools console shows the message This page includes a password or credit card input in a non-secure context. You can see an example of the browser’s warning behavior on this page. To configure Chrome to show the warning as it will appear in January 2017, open chrome://flags/#mark-non-secure-as and set the Mark non-secure origins as non-secure option to Display a verbose state when password or credit card fields are detected on an HTTP page.
Chrome canary not opening install#
To test the upcoming user experience before that time, install the latest Google Chrome Canary build. Warnings will be enabled by default for everyone in Chrome 56, slated for release in January 2017.
This document is intended to aid Web Developers in updating their sites to avoid this warning. As announced in September, Chrome will soon mark non-secure pages containing password and credit card input fields as Not Secure in the URL bar.
0 kommentar(er)
