Closed
Bug 1349969
Opened 8 years ago
Closed 4 years ago
WebSocket: don't throw for bad ports
Categories
(Core :: DOM: Networking, defect, P3)
Core
DOM: Networking
Tracking
()
RESOLVED
FIXED
84 Branch
Tracking | Status | |
---|---|---|
firefox84 | --- | fixed |
People
(Reporter: annevk, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
Instead, let the network layer handle all security checks and fail asynchronously. No need to duplicate them.
Test: https://github.com/w3c/web-platform-tests/issues/5212.
Updated•8 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Reporter | ||
Updated•4 years ago
|
Type: enhancement → defect
Component: DOM: Core & HTML → DOM: Networking
Reporter | ||
Comment 1•4 years ago
|
||
Hey Valentin, Chrome and Safari are making this change as discussed at https://github.com/web-platform-tests/wpt/pull/26392#issuecomment-721968067. Do you think we could prioritize it so we all roll out at the same time? (Potentially Freddy is interested in this as he is updating the tests?)
Flags: needinfo?(valentin.gosu)
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → valentin.gosu
Flags: needinfo?(valentin.gosu)
Whiteboard: [necko-triaged]
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Severity: normal → S3
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/f08ff116eaa4
WebSocket: don't throw for bad ports r=annevk
Comment 5•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•