[Webkit-unassigned] [Bug 32598] Flakiness in WebSocket handshake console message

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Dec 16 22:27:09 PST 2009


https://bugs.webkit.org/show_bug.cgi?id=32598





--- Comment #5 from Fumitoshi Ukai <ukai at chromium.org>  2009-12-16 22:27:08 PST ---
(In reply to comment #3)
> (From update of attachment 44952 [details])
> r=me
> 
> Is it be possible to make a reliable test for this? That would involve sending
> a large response that no reasonable implementation would coalesce into one
> didReceiveData call.

I think it would be difficult to make a reliable test.
It must send several chunks for handshake response header and each chunk should
be delivered as following order
   - first chunk. containing first line with bad response code, but not
finished whole handshake message
   - bad response code, so it closes the SocketStreamHandle.
   - before didClose comes, it receives second chunk, which would be already
queued while it is processing the first chunk.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list