- From: Patrick Meenan <notifications@github.com>
- Date: Tue, 31 Jan 2023 17:02:00 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 1 February 2023 01:02:13 UTC
FWIW, this issue persists today and popped up with a situation where we are fetching a LOT of data (several gigabytes) and storing it in application-controlled data stores (indexdb in this case). We want to bypass the local HTTP cache to avoid double-storing gigabytes worth of data but we don't want to punch a hole through intermediary caches. cache: "no-store" on requestInit does exactly what we want in Chrome and Firefox today (doesn't append Cache-Control headers) but Safari adds the Cache-Control headers. Presumably, the app could add the network headers directly if they wanted to poke holes in the network-level caches and `cache` could control the local caching behaviors. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/722#issuecomment-1411289171 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/722/1411289171@github.com>
Received on Wednesday, 1 February 2023 01:02:13 UTC