Implement $Secure- cookie prefix

This CL implements the rule that cookies whose names start with
$Secure- can only be set if the Secure attribute is enabled. The
implementation is a runtime-enabled web platform feature for now.

Intent to Implement:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/IU5t6eLuS2Y/Uq-7Kat9BwAJ

BUG=541511
TBR=droger@chromium.org

Review URL: https://codereview.chromium.org/1393193005

Cr-Commit-Position: refs/heads/master@{#354676}

1 files changed, 5 insertions, 4 deletions

diff --git a/chrome/browser/extensions/api/cookies/cookies_api.cc b/chrome/browser/extensions/api/cookies/cookies_api.cc
index 8f020919..558f90d 100644
--- a/chrome/browser/extensions/api/cookies/cookies_api.cc
+++ b/chrome/browser/extensions/api/cookies/cookies_api.cc
@@ -382,9 +382,8 @@ void CookiesSetFunction::SetCookieOnIOThread() {
   }
 
   cookie_monster->SetCookieWithDetailsAsync(
-      url_,
-      parsed_args_->details.name.get() ? *parsed_args_->details.name
-                                       : std::string(),
+      url_, parsed_args_->details.name.get() ? *parsed_args_->details.name
+                                             : std::string(),
       parsed_args_->details.value.get() ? *parsed_args_->details.value
                                         : std::string(),
       parsed_args_->details.domain.get() ? *parsed_args_->details.domain
@@ -399,7 +398,9 @@ void CookiesSetFunction::SetCookieOnIOThread() {
       // TODO(mkwst): If we decide to ship First-party-only cookies, we'll need
       // to extend the extension API to support them. For the moment, we'll set
       // all cookies as non-First-party-only.
-      false,
+      false, store_browser_context_->GetURLRequestContext()
+                 ->network_delegate()
+                 ->AreExperimentalCookieFeaturesEnabled(),
       net::COOKIE_PRIORITY_DEFAULT,
       base::Bind(&CookiesSetFunction::PullCookie, this));
 }