You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a quick read, it seems that Cache-status is only meant to be a response header.
For the Resource-freshness use case (i.e. helping fine tune the values of max-age / stale-while-revalidate), it seems that a request header is needed for the local (device) cache to share what it knows about a particular resource.
FWIW, see RFC9211, which might address some of your use case (or be extended to do so).
The text was updated successfully, but these errors were encountered: