Re: [whatwg/fetch] Allow more flexibility in how 401s/407s are handled? (#1132)

Ok, I took a look back at what I had on this. I had a [Chromium patch](https://chromium-review.googlesource.com/c/chromium/src/+/2756910) and a [Fetch patch](https://github.com/estark37/fetch/commit/b028da074e0abf5702ecac274fe91d57a7e8d19b) that look like they're in decent shape. But, to be completely honest, I remember that I discovered some problem with this approach, but now I can't remember what the problem was and of course I didn't write it down anywhere. 😫 I'm going to try to keep this in the back of my mind for the next few days and see if I magically remember what the problem was.

However, I'll note that, if I'm understanding #728 correctly, neither Fetch as currently written nor as patched above will ever return a 401/407 from HTTP-network-or-cache fetch. As currently written, HTTP-network-or-cache fetch always recurses on a 401/407 after attempting to gather credentials, and as patched above, it sometimes returns an opaque response. Does that resolve the concern in #728?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1132#issuecomment-1139831381

You are receiving this because you are subscribed to this thread.

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