Re: [whatwg/fetch] redirects and etag/if-none-match (Issue #1770)

> For reference, I think this is where chromium restricts the status code:
>
> https://source.chromium.org/chromium/chromium/src/+/main:net/http/http_cache_transaction.cc;l=3029;drc=aeeec53b304d068aa96fe84816d1d6c9d96f454e

There may be additional filtering elsewhere. From observation, the browser doesn't send `If-None-Match` headers if the original response returned an ETag but had a 206 status code.

> > 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".

Would it reasonable to _start_ with specifying "ok status" and then tightening the spec as we gain more certainty around the intended behavior? Since step 8.25.2 currently specifies no restrictions, I'd imagine we'd want to start with the smallest reasonable "logical spec diff" and incrementally proceed from there.

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

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