Closed
Bug 752778
Opened 12 years ago
Closed 12 years ago
Teach pywebsocket to send empty close frames
Categories
(Core :: Networking: WebSockets, defect)
Core
Networking: WebSockets
Tracking
()
RESOLVED
DUPLICATE
of bug 752776
People
(Reporter: jduell.mcbugs, Assigned: jduell.mcbugs)
References
Details
Attachments
(1 file, 1 obsolete file)
This is mainly for testing bug 748580. It's also a minor spec issue--the spec suggests that endpoints ought to ack close messages with a close message with the same code as received, and this isn't possible in pywebsocket w/o this patch. I've submitted the patch upstream: http://code.google.com/p/pywebsocket/issues/detail?id=123&thanks=123&ts=1336441544 Not sure I want to deal with maintaining a separate patch if they don't take it--thoughts? I guess it wouldn't be that hard. I guess we might as well hold off on reviewing this for now--if pywebsocket takes it, we can consider it reviewed...
Assignee | ||
Comment 1•12 years ago
|
||
minor fix for case where code is present but reason isn't in network msg.
Attachment #621842 -
Attachment is obsolete: true
Assignee | ||
Comment 2•12 years ago
|
||
Pywebsokcet v631 took my changes for handling empty close frames, so we'll fix this in bug 752776 by just upgrading pywebsocket.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•