Re: [whatwg/fetch] A cross-origin to same-origin redirect should not result in an opaque response (#357)

The simplest fix would be to set response tainting back to "basic".

Anything else seems to get complicated due to same-origin to cross-origin redirects. One option there is to move the logic around CORS down the stack, but it's not really clear to me that improves matters.

Note that we only mangle request's origin when CORS is in play so it should remain a fine way to check if a URL is same-origin in all other scenarios.

---
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/357#issuecomment-238795009