Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132) from Emily Stark on 2022-08-13 (public-webapps-github@w3.org from August 2022)

From: Emily Stark <notifications@github.com>
Date: Fri, 12 Aug 2022 17:16:54 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/1132/1213606759@github.com>

Finally got a chance to play with this some more; sorry for the delay. Chrome does indeed expose 407 responses to the Service Worker at the moment. Haven't tested other browsers. As previously mentioned, this isn't a problem with the spec at the moment, it's a problem in Chrome's implementation.

If we go ahead with the changes referenced in https://github.com/whatwg/fetch/issues/1132#issuecomment-1139831381, such that an opaque response is returned for 401s/407s (both in the spec and the implementation), is that sufficient to resolve #728?

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

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

Received on Saturday, 13 August 2022 00:17:07 UTC