Closed
Bug 1680733
Opened 4 years ago
Closed 4 years ago
Case-sensitive "websocket" upgrade request header check breaks WebSocket connection
Categories
(Remote Protocol :: Agent, defect, P1)
Remote Protocol
Agent
Tracking
(firefox85 fixed)
RESOLVED
FIXED
85 Branch
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
We incorrectly check the WebSocket upgrade request header and only allow websocket
:
This breaks several websocket client libraries given that also WebSocket
and WebSocket
gets send.
The value should actually be case-insensitive as this network code shows.
Assignee | ||
Comment 1•4 years ago
|
||
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0be8be3dc849
[remote] Use a case-insensitive check for WebSocket upgrade header value. r=remote-protocol-reviewers,jgraham
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
Assignee | ||
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•