- From: Patrick Meenan <notifications@github.com>
- Date: Tue, 31 Jan 2023 08:50:47 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 31 January 2023 16:50:59 UTC
The [cache mode](https://fetch.spec.whatwg.org/#concept-request-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``` and ```Cache-Control: no-cache``` to the HTTP requests, busting network caches. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1599 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1599@github.com>
Received on Tuesday, 31 January 2023 16:50:59 UTC