HttpCache: don't mess up status on range requests getting a non-200/206
We would sometimes do it to a cached 301, and then get really confused trying to read a body that wasn't there. 200 and 206 responses are the only in-caches ones (wire could also have a 304) which could possibly result in a 206 to our client, so others should just have range handling dropped; we do that already for things gotten on the wire but not from cache. Bug: 1015829 Change-Id: I6ba127aec8e88a7cbf72d7a87b94e5e7f10a3973 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899890Reviewed-by:Shivani Sharma <shivanisha@chromium.org> Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#714995}
Showing
Please register or sign in to comment