Implement $Secure- cookie prefix

chrome/browser/chrome_content_browser_client.cc

Index: chrome/browser/chrome_content_browser_client.cc
diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc
index c607c2c97040ee9081cc620b3f1ec50cf680e72a..08ccd96cb3e8d9b6e94e8ac1b047701869bf37b5 100644
--- a/chrome/browser/chrome_content_browser_client.cc
+++ b/chrome/browser/chrome_content_browser_client.cc
@@ -642,7 +642,9 @@ void CreateUsbDeviceManager(
 }  // namespace
 
 ChromeContentBrowserClient::ChromeContentBrowserClient()
-    :
+    : experimental_web_platform_features_enabled_(
+          base::CommandLine::ForCurrentProcess()
+              ->HasSwitch(switches::kEnableExperimentalWebPlatformFeatures)),

[jochen (gone - plz use gerrit), 2015/10/12 09:31:41]

that's a content switch, you can just access it in content/ without the chrome
content browser client api

[estark, 2015/10/12 09:39:19]

That might be a little weird for non-chrome content embedders, though. For
non-chrome embedders, when the experimental flag is on, prefixes will always be
enforced for cookies set from the renderer, but not for cookies received over
the network. Do you think that's okay?

       weak_factory_(this) {
 #if defined(ENABLE_PLUGINS)
   for (size_t i = 0; i < arraysize(kPredefinedAllowedDevChannelOrigins); ++i)
@@ -2697,6 +2699,10 @@ void ChromeContentBrowserClient::OverridePageVisibilityState(
   }
 }
 
+bool ChromeContentBrowserClient::ExperimentalCookieFeaturesEnabled() {
+  return experimental_web_platform_features_enabled_;
+}
+
 #if defined(ENABLE_WEBRTC)
 void ChromeContentBrowserClient::MaybeCopyDisableWebRtcEncryptionSwitch(
     base::CommandLine* to_command_line,