Set trusted SPDY proxy dynamically on per-profile basis

chrome/browser/io_thread.h

Index: chrome/browser/io_thread.h
diff --git a/chrome/browser/io_thread.h b/chrome/browser/io_thread.h
index b7ca041b63978eeeddf1ec4473125169e29ce5d3..81526bcd98f086bbabb464a17b490886fe970254 100644
--- a/chrome/browser/io_thread.h
+++ b/chrome/browser/io_thread.h
@@ -81,6 +81,7 @@ class ProxyConfigService;
 class ProxyService;
 class SSLConfigService;
 class TransportSecurityState;
+class TrustedSpdyProxyProvider;
 class URLRequestBackoffManager;
 class URLRequestContext;
 class URLRequestContextGetter;
@@ -208,7 +209,10 @@ class IOThread : public content::BrowserThreadDelegate {
     Optional<bool> enable_spdy_ping_based_connection_checking;
     Optional<net::NextProto> spdy_default_protocol;
     net::NextProtoVector next_protos;
-    Optional<std::string> trusted_spdy_proxy;
+    // |trusted_spdy_proxy_provider| provides a trusted SPDY proxy that is

[bengr, 2016/01/11 22:29:35]

There's no need to use || if what's enclosed is obviously code.

provides a trusted SPDY proxy that is allowed to push cross-origin resources ->
provides a proxy server that is allowed to use SPDY to push resources from other
origins.

[tbansal1, 2016/01/12 20:50:50]

Done.

+    // allowed to push cross-origin resources. |trusted_spdy_proxy_provider|
+    // may be NULL.
+    scoped_ptr<net::TrustedSpdyProxyProvider> trusted_spdy_proxy_provider;

[bengr, 2016/01/11 22:29:35]

I wonder if we should instead have a net::TrustedProxyProvider, so that QUIC
could use it too. 

[tbansal1, 2016/01/12 20:50:50]

Changed to TrustedSpdyProxyVerifier.

TrustedProxyProvider would not convey that this is only a HTTP2/SPDY  proxy
verifier.

     std::set<net::HostPortPair> forced_spdy_exclusions;
     Optional<bool> use_alternative_services;
     Optional<double> alternative_service_probability_threshold;