Add a new flag for HTTP-bad Phase 1 development work

components/security_state/switches.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "components/security_state/switches.h"
 
 namespace security_state {
 namespace switches {
 
 // Use to opt-in to marking HTTP as non-secure.
 const char kMarkNonSecureAs[] = "mark-non-secure-as";
 const char kMarkNonSecureAsNeutral[] = "neutral";
 const char kMarkNonSecureAsNonSecure[] = "non-secure";
+const char kMarkNonSecureWhenPasswordOrCc[] = "non-secure-passwords";

[elawrence, 2016/09/13 17:56:31]

Is this a temporary flag, or do we plan to keep it as the feature evolves? Even
in this first draft, it's somewhat misleading; maybe we could use
"non-secure-if-sensitive" or something and keep that as the experiment evolves
to other triggers?

[felt, 2016/09/13 18:39:51]

If we do other triggers beyond passwords and CC, we should use a separate flag
level for that one to keep it separate. This flag will be specific to the
rollout for phase 1 and shouldn't be repurposed.

 
 }  // namespace switches
 }  // namespace security_state