Switch to using the system request context for OCSP.
This gets rid of all the ugly "is_main" logic for URLRequestContext.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/7013071
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85555 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/io_thread.h b/chrome/browser/io_thread.h
index 0e20611..1522cfa 100644
--- a/chrome/browser/io_thread.h
+++ b/chrome/browser/io_thread.h
@@ -66,6 +66,12 @@
scoped_ptr<net::FtpTransactionFactory>
proxy_script_fetcher_ftp_transaction_factory;
scoped_ptr<net::URLSecurityManager> url_security_manager;
+ // We use a separate URLRequestContext for PAC fetches, in order to break
+ // the reference cycle:
+ // URLRequestContext=>PAC fetch=>URLRequest=>URLRequestContext.
+ // The first URLRequestContext is |system_url_request_context|. We introduce
+ // |proxy_script_fetcher_context| for the second context. It has a direct
+ // ProxyService, since we always directly connect to fetch the PAC script.
scoped_refptr<net::URLRequestContext> proxy_script_fetcher_context;
scoped_ptr<net::ProxyService> system_proxy_service;
scoped_ptr<net::HttpTransactionFactory> system_http_transaction_factory;
