Race TCP connection to proxies with QUIC connections

components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h

Index: components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h
diff --git a/components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h b/components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h
index 2cf6f7aa7381ba422295cad15bf5b4c0ff095b74..82220f758b225c954e9a6dd2788f141d8e2b6235 100644
--- a/components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h
+++ b/components/data_reduction_proxy/core/browser/data_reduction_proxy_delegate.h
@@ -61,6 +61,12 @@ class DataReductionProxyDelegate : public net::ProxyDelegate {
       const net::HostPortPair& origin,
       const net::HostPortPair& proxy_server,
       const net::HttpResponseHeaders& response_headers) override;
+  void GetAlternativeProxy(
+      const GURL& url,
+      const net::ProxyServer& resolved_proxy_server,
+      net::ProxyServer* alternative_proxy_server) const override;
+  void OnAlternativeProxyBroken(

[bengr, 2016/08/26 17:34:10]

The term "Bad" is used in the network stack. Perhaps we should call this
OnAlternativeProxyBad?

[tbansal1, 2016/08/26 17:44:48]

I think the network stack uses "Bad" for proxy and "Broken" for alternative
protocols (e.g., QUIC). It is not clear what to use for alternative protocol
proxy. I prefer "Broken" because (to me) it implies that the failure is related
to the alternative protocol, and the proxy may still be usable (through
traditional H2 protocol). 

+      const net::ProxyServer& alternative_proxy_server) override;
 
  private:
   const DataReductionProxyConfig* config_;