Re: [whatwg/fetch] Header to opt out of opaque redirect (#601)

In my SPA, my server could return a 3xx response requiring the user to reauthenticate with a third party oauth provider. The fact that there is no way for me to simply read the 'location' header and intercept the fetch redirect to do a *real* redirect instead has singlehandled put me back to using nasty XMLHttpRequests. :'( I thought we've moved on from this!

-- 
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/601#issuecomment-612495744