Re: [w3c/ServiceWorker] Service workers allow for more responses to be executed as script (#1509)

@annevk 

> That's a good twist, but a redirect to a POST with one of those response statuses will also change the request method to GET.

My memory is a bit flakey here so correct me if I'm wrong: if an opaque response redirects, the response is always opaque right?

CSP uses "error" for redirect. I guess we would enforce that for all non-GET no-cors requests.

If we're going the CORB-style route, I guess we could follow redirects by default, but create a new [response tainting](https://fetch.spec.whatwg.org/#concept-request-response-tainting) of "`no-body`", which fetch will use to discard response bodies before it re-enters the page.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1509#issuecomment-616442192