This bug tracks the addition of the new flags used by the HTTPBad Phase 2 feature announced in https://security.googleblog.com/2017/04/next-steps-toward-more-connection.html
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/528541268e541b20e632380fd22aba8aeac53521 commit 528541268e541b20e632380fd22aba8aeac53521 Author: elawrence <elawrence@chromium.org> Date: Wed May 31 04:36:01 2017 Add new mark-non-secure-as options to chrome://flags Non-secure HTTP cannot meet users’ security and privacy expectations when browsing the web. This change introduces new flag states which will control marking HTTP pages as non-secure in Incognito mode and after editing HTML forms. Subsequent CLs will detect the new flag states and adjust the Security Chip UI warnings accordingly. BUG= 721896 Review-Url: https://codereview.chromium.org/2907153006 Cr-Commit-Position: refs/heads/master@{#475803} [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/chrome/browser/about_flags.cc [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/chrome/browser/flag_descriptions.cc [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/chrome/browser/flag_descriptions.h [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/components/security_state/core/security_state.cc [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/components/security_state/core/switches.cc [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/components/security_state/core/switches.h [modify] https://crrev.com/528541268e541b20e632380fd22aba8aeac53521/tools/metrics/histograms/enums.xml
Comment 1 by elawrence@chromium.org
, May 12 2017