- From: Jake Archibald <notifications@github.com>
- Date: Tue, 19 Sep 2017 07:48:34 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 September 2017 14:49:35 UTC
I don't think this is technically needed because **CORS-preflight fetch** calls **HTTP-network-or-cache fetch**, whereas the service worker interception happens in **HTTP fetch**. Redirects aren't an issue, because **HTTP-network-or-cache fetch** doesn't follow redirects. Well, it's an issue if CORS preflights are expected to follow redirects. Are they? Setting this for safety seems fine, but maybe include a note to say it doesn't do anything right now? -- 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/pull/598#issuecomment-330564058
Received on Tuesday, 19 September 2017 14:49:35 UTC