Re: [w3c/ServiceWorker] What happens to the request body if the fetch isn't handled? (#1191)

If I remember correctly at the F2F we were happy with making the service worker use clone() to avoid breakage, but maybe that should be reconsidered. It does seem a bit weird for a 307 redirect to automatically break even if the worker didn't read the request.body.

I put together a test page here: https://aware-flame.glitch.me/

The current Chrome behavior is liable to change as we migrate to the the "servicified" architecture, which is trying to avoid needless data copies (right now we always stuff the whole request body in a new blob and hand that to the service worker, so the body survives whatever the service worker does).

In the "read from sw and then redirect 307" fetch() test, Firefox seems to get a Bad Request response but I can't determine whether that's coming from the server for some reason or from Firefox. Based on the discussion here, it should be a network error. However, for main resource (navigation) requests, the body is available after the redirect even though service worker consumed it.


-- 
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/1191#issuecomment-345617978