summaryrefslogtreecommitdiffstats
path: root/net/base
diff options
context:
space:
mode:
authorliberato <liberato@chromium.org>2015-05-29 07:19:10 -0700
committerCommit bot <commit-bot@chromium.org>2015-05-29 14:20:09 +0000
commit1f59bb3f4c02afbc538ca78e6d1f5d1b82a75b5e (patch)
treedd71d806d982c171b9dee87eb66680b66cf42718 /net/base
parent5b9b90db458ce17f17fc7e0f9cbf1078b44e2835 (diff)
downloadchromium_src-1f59bb3f4c02afbc538ca78e6d1f5d1b82a75b5e.zip
chromium_src-1f59bb3f4c02afbc538ca78e6d1f5d1b82a75b5e.tar.gz
chromium_src-1f59bb3f4c02afbc538ca78e6d1f5d1b82a75b5e.tar.bz2
Prevent unlimited re-sends of failed partial requests.
If we receive a 401 on a network request, after we've already read some data successfully, then we will retry the request. This change introduces a fixed limit (currently 1) on the number of consecutive retries. Previously, we would retry indefinitely if we continue to get 401s. We could hit this case in the case of credentials that expire part way through a read. BUG=474835 Review URL: https://codereview.chromium.org/1103563002 Cr-Commit-Position: refs/heads/master@{#331965}
Diffstat (limited to 'net/base')
-rw-r--r--net/base/net_error_list.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/net/base/net_error_list.h b/net/base/net_error_list.h
index 363b305..9133947 100644
--- a/net/base/net_error_list.h
+++ b/net/base/net_error_list.h
@@ -683,6 +683,10 @@ NET_ERROR(CACHE_CHECKSUM_MISMATCH, -408)
// Internal error code for the HTTP cache. The cache lock timeout has fired.
NET_ERROR(CACHE_LOCK_TIMEOUT, -409)
+// Received a challenge after the transaction has read some data, and the
+// credentials aren't available. There isn't a way to get them at that point.
+NET_ERROR(CACHE_AUTH_FAILURE_AFTER_READ, -410)
+
// The server's response was insecure (e.g. there was a cert error).
NET_ERROR(INSECURE_RESPONSE, -501)