Do cookie checks in NetworkDelegate instead of the URLRequest::Delegate.

content/common/net/url_fetcher_impl_unittest.cc

Index: content/common/net/url_fetcher_impl_unittest.cc
diff --git a/content/common/net/url_fetcher_impl_unittest.cc b/content/common/net/url_fetcher_impl_unittest.cc
index 909bb6f0247c24a93797f79b0b55c9c8feb1e940..edb2c01a9d5171824dba644627b72f7856c762d3 100644
--- a/content/common/net/url_fetcher_impl_unittest.cc
+++ b/content/common/net/url_fetcher_impl_unittest.cc
@@ -461,8 +461,9 @@ void URLFetcherProtectTest::OnURLFetchComplete(
     static int count = 0;
     count++;
     if (count < 20) {
-      fetcher_->StartWithRequestContextGetter(new TestURLRequestContextGetter(
-          io_message_loop_proxy()));
+      fetcher_->SetRequestContext(
+          new TestURLRequestContextGetter(io_message_loop_proxy()));
+      fetcher_->Start();
     } else {
       // We have already sent 20 requests continuously. And we expect that
       // it takes more than 1 second due to the overload protection settings.
@@ -572,8 +573,9 @@ void URLFetcherMultipleAttemptTest::OnURLFetchComplete(
   EXPECT_FALSE(data.empty());
   if (!data.empty() && data_.empty()) {
     data_ = data;
-    fetcher_->StartWithRequestContextGetter(

[willchan no longer on Chromium, 2012/03/06 02:59:01]

Why did this change? OIC, they're functionally equivalent. I coulda sworn when I
introduced this back in the day, they were different and this was
necessary...but I guess not. OK, seems fine.

+    fetcher_->SetRequestContext(
         new TestURLRequestContextGetter(io_message_loop_proxy()));
+    fetcher_->Start();
   } else {
     EXPECT_EQ(data, data_);
     delete fetcher_;  // Have to delete this here and not in the destructor,