Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770) from Anne van Kesteren on 2024-12-19 (public-webapps-github@w3.org from December 2024)

From: Anne van Kesteren <notifications@github.com>
Date: Wed, 18 Dec 2024 23:38:34 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/1770/2552979008@github.com>

I initially thought that would go against the specification (as Mark did mention revalidation above, which is what you're talking about), but https://httpwg.org/specs/rfc9111.html#rfc.section.4.3 does suggest to me that revalidation is optional (emphasis mine):

> it **can** use the conditional request mechanism

It seems that we could decide that for the web platform that while we can cache all status codes, we're not going to validate all of them as we don't believe that to be useful or web compatible.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1770#issuecomment-2552979008
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1770/2552979008@github.com>

Received on Thursday, 19 December 2024 07:38:38 UTC