Response.redirected state is not propagated through FetchEvent.respondWith() to outer fetch() result

RESOLVED FIXED

Status

()

defect
P2
normal
RESOLVED FIXED
2 years ago
a year ago

People

(Reporter: bkelly, Unassigned)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

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.
The correct fix to this is to probably finally implement bug 1222008.
Depends on: 1222008
Priority: -- → P2
I think Tom fixed this in bug 122008.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.