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

Currently `opaque` means its a cross-origin response loaded without CORS.  So we have a hard block on supporting those for navigations.  See step 3.2.3 here:

https://fetch.spec.whatwg.org/#http-fetch

My skim of the issue suggested to me these would be same-origin to the request url and return a 40x status code.  In that regard they are very similar to navigation redirects.  When redirect mode is `manual`, like during navigation, we return an `opaqueredirect` instead that allows the status code to flow to the outer navigation machinery while hiding the location header and whatnot from the SW script.

The parallels just made me wonder if we should build something similar for auth.  That seems like an easier path than trying to use `opaque`.

But its certainly possible I misunderstood and these are cross-origin?

-- 
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/1132#issuecomment-777819799