Re: [w3c/ServiceWorker] The network fallback should be rejected when the request body is locked or disturbed (#1560)

With non-streaming body Chromium copies the request body. With streaming body it crashes.

If there are no compatibility concerns I think failing the request always is a more consistent (and hence better) behavior. I'm trying to measure the impact of that change: https://chromium-review.googlesource.com/c/chromium/src/+/2631550

-- 
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/1560#issuecomment-762059534