Retry HttpNetworkTransactions upon receipt of ERR_NETWORK_CHANGED during host resolution and …

net/url_request/url_fetcher_core.cc

Index: net/url_request/url_fetcher_core.cc
diff --git a/net/url_request/url_fetcher_core.cc b/net/url_request/url_fetcher_core.cc
index e2fcc450219e50585bb9a57e932f116d700c6dc8..18cc87f31d5850bd6866c096b60ab3f282b9ad38 100644
--- a/net/url_request/url_fetcher_core.cc
+++ b/net/url_request/url_fetcher_core.cc
@@ -521,6 +521,10 @@ void URLFetcherCore::StartURLRequest() {
     request_->SetUserData(url_request_data_key_,
                           url_request_create_data_callback_.Run());
   }
+  // Don't duplicate retrying in both URLFetcher and URLRequest as this can have
+  // a multiplicative effect.
+  if (max_retries_on_network_changes_)

[mmenke, 2014/02/13 20:20:17]

I think it's weird to have two ways to do this.  Admittedly, this implementation
will re-send requests, even rePOSTing if needed, but I'm not a huge fan of
having two mechanisms to do this.  May not have a choice, though.  Should look
at callsites, I think.

+    request_->set_max_automatic_retries_on_network_changes(0);
 
   switch (request_type_) {
     case URLFetcher::GET: