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

> Isn't that the opposite of what we want to be doing?

My bad, I'd assumed navigate created a new request for each phase of the redirect, so it wouldn't retain the `skip-service-worker` flag.

Is there any value in making an opaque redirect response work in response to a "follow" request? It could work like this: (using https://fetch.spec.whatwg.org/#http-fetch)

**Request with redirect mode "follow"**

* Step 2.1: ask SW for a response, get an opaque redirect back.
* Because this is an opaque redirect & not a client request context, set `skip-service-worker` flag
* Step 4.301.10: follow the redirect, without consulting the SW

**Request with redirect mode "manual"**

* Step 2.1: ask SW for a response, get an opaque redirect back.
* Because this is a client request context, the `skip-service-worker` flag is not set
* The redirect is returned to the navigate algorithm, and go through a SW



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