summaryrefslogtreecommitdiffstats
path: root/net/proxy/proxy_config_service_linux_unittest.cc
diff options
context:
space:
mode:
authoreroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-08 04:05:10 +0000
committereroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-08 04:05:10 +0000
commitbd45292e5c21fcb3fef1fd5dfb8207ae29277f8a (patch)
tree1eca5cafa1a1b87a5f5182f1d7f12aaf588fc809 /net/proxy/proxy_config_service_linux_unittest.cc
parent3ffe71e020ea8e3597c2835f1ba0ebb8fb85ab9e (diff)
downloadchromium_src-bd45292e5c21fcb3fef1fd5dfb8207ae29277f8a.zip
chromium_src-bd45292e5c21fcb3fef1fd5dfb8207ae29277f8a.tar.gz
chromium_src-bd45292e5c21fcb3fef1fd5dfb8207ae29277f8a.tar.bz2
Adds a NetworkChangeNotifier dependency to ProxyService; when we observer a network change through the notifier, the ProxyService re-configures itself.
So for example, if you were to switch to VPN and are using a custom PAC URL, we will re-download that URL on the new network. Similarly if you are using auto-detect PAC settings, we will re-run the autodiscovery steps for the next resolve. Note that Chromium is still passing a NULL NetworkChangeNotifier dependency into its ProxyService -- until it passes a real implementation, this will not impact Chrome. BUG=12293 TEST=ProxyServiceTest.NetworkChangeTriggersPacRefetch Review URL: http://codereview.chromium.org/525104 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35772 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/proxy/proxy_config_service_linux_unittest.cc')
0 files changed, 0 insertions, 0 deletions