Disable HTTP2 websockets until we can resolve proxy issues.
Categories
(Core :: Networking: WebSockets, defect, P1)
Tracking
()
People
(Reporter: valentin, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][necko-priority-queue])
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
It seems using HTTP2 websockets with a HTTP2 proxy can sometimes cause WS to not work, or even crashes.
We should disable this until we can fix it and get CI to test this exact scenario to avoid regressions.
Reporter | ||
Comment 1•11 months ago
|
||
Assignee | ||
Comment 2•11 months ago
|
||
Updated•11 months ago
|
Reporter | ||
Updated•11 months ago
|
Comment 4•11 months ago
|
||
Backed out for causing failure on test_websocket_http2.html
Assignee | ||
Comment 5•11 months ago
|
||
Comment 7•11 months ago
|
||
bugherder |
Assignee | ||
Comment 9•11 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D194871
Updated•11 months ago
|
Comment 10•11 months ago
|
||
Uplift Approval Request
- Risk associated with taking this patch: No risk. This patch is basically a pref flip.
- String changes made/needed: N/A
- Needs manual QE test: no
- User impact if declined: Possible crash
- Fix verified in Nightly: yes
- Steps to reproduce for manual QE testing: N/A
- Explanation of risk level: Low
- Is Android affected?: yes
- Code covered by automated testing: yes
Assignee | ||
Updated•11 months ago
|
Comment 11•11 months ago
|
||
Comment on attachment 9366254 [details]
Bug 1867006 - Disable HTTP2 websockets until we can resolve proxy issues. r=#necko
Approved for 121.0b6.
Updated•11 months ago
|
Comment 12•11 months ago
|
||
uplift |
Comment 13•9 months ago
|
||
Is it possible to backport this fix to Firefox ESR? (or backport the patch in bug 1848013, whatever is easier or more relevant)
My team meets lots of Firefox users who cannot use a service relying on Websocket exclusively because of what has been reported in bug 1848013 (their websocket connections pass through a squid Proxy). It really penalizes them.
Updated•9 months ago
|
Assignee | ||
Comment 14•9 months ago
|
||
I've requested to uplift the patch in bug 1848013 to ESR.
Comment 15•9 months ago
•
|
||
Thank you Kershaw!
Description
•