Closed Bug 1412002 Opened 3 years ago Closed 3 years ago
.redirected state is not propagated through Fetch Event .respond With() to outer fetch() result
We currently fail this WPT test: https://searchfox.org/mozilla-central/source/testing/web-platform/tests/service-workers/service-worker/redirected-response.https.html#129 This is because the SW fetch() gets a Response with .redirected=true. When we pass that to respondWith() we don't force the outer resulting Response to also have .redirected=true. Currently .redirected=true is set based on redirect callbacks firing. I don't think we want to do that for this synthetic case. We probably need some way of forcing the synthetic redirected state through the channel.
I think Tom fixed this in bug 122008.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.