New issue
Advanced search Search tips

Issue 784520 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Avoiding entry open of zero-fresshness resources breaks --show-saved-copy

Project Member Reported by morlovich@chromium.org, Nov 13 2017

Issue description

https://chromium-review.googlesource.com/c/chromium/src/+/732841 (pending at time of writing) introduces an optimization where cache entries that 
have headers that provide for no way of reuse (zero max age, no etag or last-modified) are not opened, replacing the expensive open operation with a more asynchronous doom + create sequence, which can be overlapped with network request for the resource.  That breaks the command-line-flag enableable option of letting users open stale versions of resources from error page when HTML pages meet that criterion, since they get doomed as useless on first attempt.

 

Sign in to add a comment