Closed
Bug 711886
Opened 13 years ago
Closed 8 years ago
Refuse connection if server replies with non-matching subprotocol
Categories
(Core :: Networking: WebSockets, defect)
Core
Networking: WebSockets
Tracking
()
RESOLVED
FIXED
mozilla55
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | fixed |
People
(Reporter: jduell.mcbugs, Assigned: CuveeHsu)
Details
(Whiteboard: [http-conn][necko-active])
Attachments
(1 file, 2 obsolete files)
|
6.65 KB,
patch
|
CuveeHsu
:
review+
|
Details | Diff | Splinter Review |
Splitting out from bug 666349 attachment 582496 [details] [diff] [review] (carring forward patrick's +r)
The test for this is currently failing on some tryservers (mainly linux, but I've seen windows too). The symptom is that the WS connection hangs instead of failing.
I suspect some sort of pywebsocket issue (maybe python version specific?) is causing the server to barf w/o failing the connection, so we hang.
As an extra piece of fun, the mochitest harness reports this as
ERROR TEST-UNEXPECTED-FAIL | test_websocket.html | Test timed out.
TEST-END | /tests/content/base/test/test_websocket.html | finished in 325819ms
ERROR TEST-UNEXPECTED-FAIL | test_websocket_basic.html | Should get error in test-47!
i.e it's wrongly reporting the test as being in test_websocket_basic.html.
I'm gonna try this on python 2.5 and see what happens.
Attachment #582716 -
Flags: review+
Updated•13 years ago
|
Whiteboard: [http-conn]
Comment 1•12 years ago
|
||
Hi Jason, do you still see the bug of pywebsocket which prevented this change from being committed?
Comment 2•10 years ago
|
||
Bug still present in 37
Comment 3•9 years ago
|
||
jason, we should get this landed - right?
Assignee: nobody → jduell.mcbugs
Flags: needinfo?(jduell.mcbugs)
Whiteboard: [http-conn] → [http-conn][necko-active]
Comment 4•9 years ago
|
||
In HyBi ML, there we're seeing rough rough consensus on that subprotocol comparison should be made case-sensitively.
See this thread http://www.ietf.org/mail-archive/web/hybi/current/threads.html#10719
I summarized interoperability issue between Chromium and Firefox in this post.
http://www.ietf.org/mail-archive/web/hybi/current/msg10727.html
| Reporter | ||
Comment 5•9 years ago
|
||
Attachment #582716 -
Attachment is obsolete: true
Flags: needinfo?(jduell.mcbugs)
Attachment #8751348 -
Flags: review+
Backed out for bustage: https://treeherder.mozilla.org/logviewer.html#?job_id=27674070&repo=mozilla-inbound
https://hg.mozilla.org/integration/mozilla-inbound/rev/2da14459ec0f
Flags: needinfo?(jduell.mcbugs)
| Reporter | ||
Comment 8•8 years ago
|
||
Michal, please take a look at this at some point when you've got cycles. IIRC if you push this to try again you'll see that we have a web spec test that for some reason thinks that the comparison should be case-insensitive, in contrast to comment 4. I.e. I think it may just be a test change needed to land this.
Flags: needinfo?(jduell.mcbugs) → needinfo?(michal.novotny)
Comment 9•8 years ago
|
||
Junior is going to take a look at it.
Assignee: jduell.mcbugs → juhsu
Flags: needinfo?(michal.novotny)
| Assignee | ||
Comment 10•8 years ago
|
||
Fix bustage, carry r+
https://treeherder.mozilla.org/#/jobs?repo=try&revision=f04c8081f344c2bb3db76ff15178ea9ed3d6c10e
Attachment #8751348 -
Attachment is obsolete: true
Attachment #8861821 -
Flags: review+
| Assignee | ||
Updated•8 years ago
|
Keywords: checkin-needed
Updated•8 years ago
|
Attachment #8861821 -
Attachment is patch: true
Comment 11•8 years ago
|
||
Pushed by cbook@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9a3a29341427
Fail Websocket if server replies with non-matching subprotocol, r=mcmanus
Keywords: checkin-needed
Comment 12•8 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•