Issue 103316 in chromium: WebSocket always receiving continuation frame

215 views
Skip to first unread message

chro...@googlecode.com

unread,
Nov 7, 2011, 9:08:32 PM11/7/11
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: OS-Mac Area-Undefined Pri-2 Type-Bug

New issue 103316 by alexande...@gmail.com: WebSocket always receiving
continuation frame
http://code.google.com/p/chromium/issues/detail?id=103316

Chrome Version : 15.0.874.106
OS Version: OS X 10.7.2
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:

What steps will reproduce the problem?
1. Complete handshake
2. Receive frame from client (masked)
3. Send text frame to client (unmasked)

What is the expected result?
Client receives text frame, triggering .onmessage()

What happens instead?
"Received unexpected continuation frame." alert in console.

The client identifies a continuation frame regardless of what the opcode is
set to (have tested setting it to 0 then 1). Have disabled features such as
tcp offloading which was giving incorrect checksums but no change.
Handshake works fine. I've managed to unwrap frames without a problem.
Messages included within the handshake also work fine (as shown by 'hello'
in screenshot and .onmessage() triggered in console).

Am trying to build a WebSocket server. Can supply code if necessary but
everything should be clear in the tcpdump.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2)
AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2


Attachments:
Screen Shot 2011-11-08 at 00.57.41.png 121 KB
tcpdump.txt 3.7 KB

chro...@googlecode.com

unread,
Nov 7, 2011, 10:41:32 PM11/7/11
to chromi...@chromium.org
Updates:
Labels: -Area-Undefined Area-WebKit WebKit-WebSockets

Comment #1 on issue 103316 by tk...@chromium.org: WebSocket always

(No comment was entered for this change.)

chro...@googlecode.com

unread,
Nov 8, 2011, 5:49:15 AM11/8/11
to chromi...@chromium.org

Comment #3 on issue 103316 by alexande...@gmail.com: WebSocket always

Indeed there is! Sorry for wasting time, spent forever looking at it.
Consider this one 'fixed' then. Thanks.

Reply all
Reply to author
Forward
0 new messages