| commit | 27d2e5e5e2eb429943a27b4c23cf120733ea39a7 | |
| author | cbentzel <cbentzel@chromium.org> | |
| Fri, 10 Jul 2015 17:39:56 +0000 (10 10:39 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 10 Jul 2015 17:40:37 +0000 (10 17:40 +0000) | ||
| tree | d1bc899825a1f2feeda71eb87238ef0f413245ad | treesnapshot (tar.gz zip) |
| parent | 6baec756afca1f9949f6ff0e0252dd070bb86349 | commitdiff |
Add Net.ProxyScriptFetchSuccessDuration UMA to record how long PAC script fetches take.
Currently PAC script fetches time out after 5 minutes. It's possible that this was a much higher value than needed.
This limit is also problematic in certain cases. For example, if a PAC script is retrieved over HTTPS, and the computer recently joined a network which has a captive portal that blackholes all HTTPS traffic then that user will be unable to sign in to the captive portal with Chrome while waiting for the limit to be hit.
BUG=251682
Review URL: https://codereview.chromium.org/1224343002
Cr-Commit-Position: refs/heads/master@{#338314}
Currently PAC script fetches time out after 5 minutes. It's possible that this was a much higher value than needed.
This limit is also problematic in certain cases. For example, if a PAC script is retrieved over HTTPS, and the computer recently joined a network which has a captive portal that blackholes all HTTPS traffic then that user will be unable to sign in to the captive portal with Chrome while waiting for the limit to be hit.
BUG=251682
Review URL: https://codereview.chromium.org/1224343002
Cr-Commit-Position: refs/heads/master@{#338314}
| net/proxy/proxy_script_fetcher_impl.cc | diffblobblamehistory | |
| net/proxy/proxy_script_fetcher_impl.h | diffblobblamehistory | |
| tools/metrics/histograms/histograms.xml | diffblobblamehistory |