Disabled resource scheduling when using a SPDY proxy

net/url_request/url_request.h

Index: net/url_request/url_request.h
diff --git a/net/url_request/url_request.h b/net/url_request/url_request.h
index 119fbd98d097c47527988a647a6ea5506bea38a8..84971141cc5c80f7c6e100111f81536491b1224c 100644
--- a/net/url_request/url_request.h
+++ b/net/url_request/url_request.h
@@ -500,6 +500,11 @@ class NET_EXPORT URLRequest : NON_EXPORTED_BASE(public base::NonThreadSafe),
     return response_info_.was_fetched_via_proxy;
   }
 
+  // Returns true if the URLRequest was delivered over SPDY.

[willchan no longer on Chromium, 2014/01/08 19:03:09]

I'm mostly fine with this, but it might be the time for us to do a rename. Is
this set to true for SPDY proxies & origins? Does your code care to
differentiate?

[Pat Meenan, 2014/01/08 19:10:57]

It is true for both cases, the flag gets set as long as the request was routed
over a SPDY connection (which works fine for my case - tested both scenarios
just to be sure).

+  bool was_fetched_via_spdy() const {
+    return response_info_.was_fetched_via_spdy;
+  }
+
   // Returns the host and port that the content was fetched from.  See
   // http_response_info.h for caveats relating to cached content.
   HostPortPair GetSocketAddress() const;