Service worker respondWith uses HTTP/1.1
Categories
(Core :: DOM: Service Workers, defect)
Tracking
()
People
(Reporter: pinconquentin, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:135.0) Gecko/20100101 Firefox/135.0
Steps to reproduce:
Register a service worker, intercepting all fetch events, and use event.respondWith(fetch(event.request)) from the service worker 'fetch' listener to actually perform the request.
Actual results:
If the queries server supports HTTP/2 or 3, it should use this protocol. Instead, in the network tab, the query is marked as made using HTTP/1.1
Expected results:
The same HTTP protocol should be used with or without using respondWith
| Reporter | ||
Comment 1•1 year ago
|
||
Content of about:support
| Reporter | ||
Comment 2•1 year ago
|
||
Comment on attachment 9466182 [details]
Reproduction
Reproduction
| Reporter | ||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 4•11 months ago
|
||
I think the implementation belongs in mozilla::dom::ServiceWorkerManager::DispatchFetchEvent, but I'm not 100% sure.
Olli, if you think this is a but in Necko, please move it back. I'd appreciate a brief outline of how service worker fetches are piped back into intercepted HTTP channel.
Updated•11 months ago
|
Updated•4 months ago
|
Description
•