Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(156)

Issue 1212643009: Allow for an existing bad proxy to be given a new retry delay. (Closed)

Created:
5 years, 5 months ago by sclittle
Modified:
5 years, 5 months ago
Reviewers:
CC:
chromium-reviews, cbentzel+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@2403
Target Ref:
refs/pending/branch-heads/2403
Project:
chromium
Visibility:
Public.

Description

Allow for an existing bad proxy to be given a new retry delay. Before this CL, any proxy that was previously marked as bad could not be assigned a different retry delay, and could only be marked as bad for the previous retry delay. This CL changes the proxy retry map update logic to replace the existing bad proxy retry info if the new retry time is later than the existing retry time. BUG=500738 Review URL: https://codereview.chromium.org/1191823002 Cr-Commit-Position: refs/heads/master@{#336451} (cherry picked from commit 08141d98705bc3a7ad0e53e64408adbf065eb554) Committed: https://chromium.googlesource.com/chromium/src/+/593db960e03bf850c2444b2dc13ede937c421afc

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+63 lines, -6 lines) Patch
M net/proxy/proxy_list.cc View 1 chunk +3 lines, -6 lines 0 comments Download
M net/proxy/proxy_list_unittest.cc View 1 chunk +60 lines, -0 lines 0 comments Download

Messages

Total messages: 1 (0 generated)
sclittle
5 years, 5 months ago (2015-06-30 00:33:29 UTC) #1
Message was sent while issue was closed.
Committed patchset #1 (id:1) manually as
593db960e03bf850c2444b2dc13ede937c421afc.

Powered by Google App Engine
This is Rietveld 408576698