Issue 97026 in chromium: WebSocket unexpectedly throws error: One or more reserved bits are on

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined OS-Windows

New issue 97026 by piotr...@gmail.com: WebSocket unexpectedly throws error:
One or more reserved bits are on
http://code.google.com/p/chromium/issues/detail?id=97026

Chrome Version : 14.0.835.163
URLs (if applicable) : ws://websocket.mtgox.com/mtgox
Other browsers tested: OK

To reproduce you can do i.e.:

1. Install Simple WebSocket Client extension from
https://chrome.google.com/webstore/detail/pfdhoblngboilpfeibdedpjgfnlcodoo

2. Click on the extension's icon

3. Enter URL: ws://websocket.mtgox.com/mtgox

4. Click "Open".

5. See the java script console.

The expected result is to keep receiving WebSocket messages. Instead the
browser reports error "One or more reserved bits are on: ..." and closes
the WebSocket connection.

Chrome 13.x did it properly.
In 14.x something is obviously broken.
I tested it only on Windows, it might also be a problem on other platforms.

Attachments:
websocket-error.png 68.8 KB

[chro...@googlecode.com]

Updates:
Labels: -Area-Undefined WebKit-WebSockets

Comment #1 on issue 97026 by will...@chromium.org: WebSocket unexpectedly

throws error: One or more reserved bits are on
http://code.google.com/p/chromium/issues/detail?id=97026

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: WontFix
Owner: tyosh...@chromium.org
Cc: yu...@chromium.org

Comment #2 on issue 97026 by tyosh...@chromium.org: WebSocket unexpectedly

throws error: One or more reserved bits are on
http://code.google.com/p/chromium/issues/detail?id=97026

It seems that websocket.mtgox.com is sending out a frame in old format
(http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-00).
Chrome 14 uses new version WebSocket protocol
(http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-08). We've
dropped old protocol and are asking servers to adopt new one. mtgox is
replying new version handshake correctly. Only new frame support looks
broken.