-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify cache mode impact on request headers #1599
Comments
@mnot thanks. Guess the issue continues and I'll comment over there. I assume the devs could add the Cache-Control header themselves directly if they want it down-stream. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The cache mode for fetch requests refers to the HTTP cache which I assume is the local cache but doesn't appear to specify what the downstream effects should be (specifically if any headers should or should not be set on outbound requests).
Maybe it';s just an interop issue with the need for web platform tests but the browsers currently differ when doing
fetch(url, {cache: "no-store"})
.Firefox and Chrome treat it as a local directive and skip the HTTP cache but send the request to the network with no change in headers.
Safari appears to treat it as a global directive to skip all caches and adds
Pragma: no-cache
andCache-Control: no-cache
to the HTTP requests, busting network caches.The text was updated successfully, but these errors were encountered: