New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 611049 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Re-evaluate cacheability of responses by status code.

Project Member Reported by gavinp@chromium.org, May 11 2016

Issue description

RFC 7231 has been out for a while, and Chrome seems to have fallen well behind other browsers in which status codes are cacheable. Recently we fixed  issue 469675 , in which we were not caching redirects that had cookies, because of excessive historic caution.

I believe even after our fix to 469675, we are less aggressive than other browsers in caching 303s and 307s, which we never cache heuristically.

Let's go over all status codes again and make sure we're caching as much as we can.
 

Sign in to add a comment