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

### What is the issue with the Fetch Standard?

@mrpickles and I were looking into how redirects and http caching work together recently.  We noticed that redirects (301/302) don't seem to send `if-none-match` headers even if the redirect response contains an etag.  This behavior seems consistent across chrome, firefox, and safari.

Does the spec currently reflect this?  I can't seem to find where it defines this restriction.  Step 25.2.2.2.1 of [http-network-or-cache-fetch](https://fetch.spec.whatwg.org/#http-network-or-cache-fetch) doesn't seem to check the status code of the stored response at all.  I also don't see it in the http-caching RFC. Am I missing it somewhere or do we need to add this check to the spec?

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

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

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