Re: [fetch] Allow "manual" redirect fetches with caveats (#66)

> and exposure of url as that is identical to the request url

Can't figure out why this is needed/useful.

> We could then enforce that you can only return such a "redirect" response to navigation request contexts (that have redirect mode on manual), coupled with a same-origin restriction.

Do we need to enforce this? If the SW returns an opaque redirect, the skip-service-worker flag could be set on the request. Doesn't this do the right thing?

> I don't see any obvious issues with this, other than perhaps the difficulty for the "navigate" algorithm to handle redirects by itself

We have to do that anyway though, right? Doesn't that algorithm have to handle redirects already?

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