hint: Allow `stale-while-revalidate` (and `stale-if-error`?) Cache-Control extensions

I believe these directives were dismissed at some point due to no browser support, however there’s increasing support for stale-while-revalidate.

stale-if-error on the other hand isn’t directly supported by browsers, though some CDNs such as Fastly and KeyCDN support it, see the support table in https://www.ctrl.blog/entry/cdn-rfc5861-support.html.

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 2
  • Comments: 28 (15 by maintainers)

Most upvoted comments

This issue is still present; reading the associated PR #4047 I checked MDN and I see that:

  1. Every browser but Safari supports it
  2. It is useful for mid-tier caches (as in proxy caches, to not delay queries while the mid-tier caches fetches from the origin) anyway
  3. Even on browsers that don’t support it, it doesn’t cause any harm either

Given this, I fail to see a good reason to not include it

stale-while-revalidate got adopted by Chrome and Firefox, so that should definitely be supported now.
stale-if-error while not supported, yet, should not be “breaking” anything as well. I mean, if a browser starts supporting it - it will use it. If it does not support it - it will ignore it. So no need to alert about it at this point. If it will be deprecated, then an alert can be added, but its wording will need to be different.