Summary: | Connection must be closed in case of Web Socket handshake error | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Yuzo Fujishima <yuzo> | ||||
Component: | WebKit Misc. | Assignee: | Alexey Proskuryakov <ap> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, eric, ukai, yuzo | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Yuzo Fujishima
2009-11-18 20:53:36 PST
Note: this bug was found while examining: https://bugs.webkit.org/show_bug.cgi?id=31465 Yuzo I don't understand what exactly fails here. According to <http://build.webkit.org/waterfall>, all tests currently pass. Does this particular test have identical output in success and failure cases? Or does it only fail with a patch from bug 31465 applied? Without 31465, the server calls a non-existent method, raises exception, and closes the socket. With 31645, the server writes an invalid handshake response to the socket. It seems that the client side can handle the socket closure case properly but not the invalid response case -- the client times out for the latter. Yuzo Sorry, s/31645/31465/g in #3. Created attachment 44045 [details]
proposed fix
Comment on attachment 44045 [details]
proposed fix
r=me
Committed <http://trac.webkit.org/changeset/51516>. |