On Tue, Dec 1, 2015 at 12:15 PM, Graham Leggett <[email protected]> wrote: >> I've been looking at an issue where a revalidation >> of a stale cache entry fails because the 304 response >> on the revalidation doesn't contain its own CC or Expires >> but the URL has a query string. This kicks the revalidation >> response out of the cache save filter early and we never >> get to look at the stale handle and update the headers. > > As I recall there is a specific code path for responses that say "we've asked > for revalidation, revalidation was successful but not cacheable. Return > cached data but invalidate it, it is the best we can do".
You're right, I missed that when comparing to my snapshot. It's prefixed by the "Hold the phone..." comment. -- Eric Covener [email protected]
