- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 26 Aug 2024 10:11:29 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 26 August 2024 17:11:33 UTC
> What does 304 translating to a 200 mean? We end up replacing a 304 network response with its stored response (so that a fetch caller almost never sees a 304, unless they control the revalidating headers themselves). We currently don't assert that the stored response has a 200 status code, but I think the HTTP specifications do end up requiring that. Might need to be further clarified as well. @mnot's input on this would be appreciated. > Does something like https://github.com/MrPickles/fetch/commit/92fee8d25c509b930cbe20541c470d679f6cfaac look to be on the right track? That does look good, modulo whether we should check for "ok status", "200", or "200 or 206". -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1770#issuecomment-2310677069 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1770/2310677069@github.com>
Received on Monday, 26 August 2024 17:11:33 UTC