- From: Mark Nottingham <notifications@github.com>
- Date: Mon, 07 Oct 2024 16:17:47 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 7 October 2024 23:17:51 UTC
> For example, why would a browser want to cache if there's a 500? > And 200 and 206 are the only status codes that imply that there's content to cache. Non-200 status codes can be [stored and revalidated](https://httpwg.org/specs/rfc9111.html#response.cacheability), and [are in practice](https://cache-tests.fyi/#status). Please don't deviate from the HTTP caching spec without good reason - reinventing it causes interop issues with non-browser caches. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1770#issuecomment-2398119983 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1770/2398119983@github.com>
Received on Monday, 7 October 2024 23:17:51 UTC