Better support with stale-while-revalidate

[daisuke.fujimura]

As discussed in other topics, current behavior of stale-while-revalidate seems to be unexpected to users including me.

This document says first request after max-age will be used to revalidate:

Indicates that it is fresh for 600 seconds, and it may continue to be served stale for up to an additional 30 seconds to parallel requests for the same resource while the initial synchronous revalidation is attempted.

but, I’d like to get stale response by the first request. As I see, this will be the common understanding of what stale-while-revalidate does.

Past topics:

• Does stale-while-revalidate work?
• High number of requests to origin for the same resource - #21 by stephane

[dfabulich]

As I wrote on the thread:

@dfabulich

[Cloudflare] doesn’t understand the stale-while-revalidate directive, and they wrongly think they’re compliant because SWR is an optional cache header, so doing entirely the wrong thing is enough for them. It’s infuriating that they’re pushing people to their paid workers plan to get actual SWR support.