Re: [whatwg/fetch] Access-Control-Max-Age not effective in preflight request caching when Authorization header is programatically defined (#1278) from Anne van Kesteren on 2021-09-29 (public-webapps-github@w3.org from September 2021)

From: Anne van Kesteren <notifications@github.com>
Date: Wed, 29 Sep 2021 01:44:35 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/1278/929968095@github.com>

There's multiple things going on here.

1. Implementations have a bug in that they do not enforce listing `Authorization` explicitly. This is being worked on by @yutakahirano, see https://groups.google.com/a/chromium.org/g/blink-dev/c/jEV2VMVjMt8/m/rogFnr6xAgAJ.
2. It seems however that they might enforce this for the preflight cache? I think that would explain the results you are seeing above. Enabling credentials mode does not really matter I think as the side effect of that is that you have to list the header, which I suspect is what matters here.

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

Received on Wednesday, 29 September 2021 08:44:47 UTC