Closed
Bug 1404041
Opened 7 years ago
Closed 6 years ago
consider if Range header should be exposed on FetchEvent.request
Categories
(Core :: DOM: Service Workers, enhancement, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1465074
People
(Reporter: bkelly, Unassigned)
Details
Currently we never expose the Range header on FetchEvent.request. This is because its added down in the http cache and network path here: https://searchfox.org/mozilla-central/source/netwerk/protocol/http/nsHttpChannel.cpp#4208 Its unclear if this should ever be exposed to script in FetchEvent.request. I filed a spec issue about that here: https://github.com/w3c/ServiceWorker/issues/1201
Reporter | ||
Updated•7 years ago
|
Blocks: ServiceWorkers-compat
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•6 years ago
|
||
This is being spec'd. See bug 1465074.
No longer blocks: ServiceWorkers-compat
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Comment 2•3 years ago
|
||
(In reply to Ben Kelly [:bkelly, not reviewing] from comment #0)
Currently we never expose the Range header on FetchEvent.request. This is
because its added down in the http cache and network path here:
https://hg.mozilla.org/mozilla-central/annotate/560296786c0cefbc749f54b20ba8afcd79ffd12a/netwerk/protocol/http/nsHttpChannel.cpp#l4208 is used for nsIResumableChannel#resumeAt()
.
But media elements have their own code to add a Range header, which does not do any checking of validators.
You need to log in
before you can comment on or make changes to this bug.
Description
•