Chrome Dev (14.0.835.8): "WebSocket is closed before the connection is established."

[ruimarinho]

Hi all,

Using the Chrome Dev (osx) channel I noticed that websockets are not working anymore with socket.io 0.6.18. I'm not sure if the 0.6 branch is still maintained and if this problem still exists on the 0.7 branch.

I cannot confirm if this is related to this Chrome update, but according to the SVN revision log, the implementation of the newer hybi-10 protocol is mentioned:

Enable hybi WebSocket protocol by default.

This CL enables the new WebSocket protocol by overriding the value of WebCore::Settings::useHixie76WebSocketProtocol() to false.

It is known that WebSocket instances initialized in worker context use the old hixie76 protocol even after this change is applied (see https://bugs.webkit.org/show_bug.cgi?id=64852). I'm going to take care of it after this CL is committed.

On the Chrome inspector, this error is logged:

WebSocket is closed before the connection is established.

On node.js console, the following message appears:

WebSocket connection invalid or Origin not verified

On Chrome Stable (12.0.742.122), presumably using hybi-09, everything is working fine.

If it's confirmed that the problem relies on the lack of support for hybi-10, can we expect it to be supported later on and backported to the 0.6 branch?

Update: Just noticed issue #429 mentions this issue too, although some of the questions rised on this ticket are still pertinent (regarding 0.6 backport, at least).

Thanks!

[perezd]

I am experiencing the same issue. We will definitely need this to be backported.

[tisba]

same problem with 15.0.854.0 dev :-/

[theturtle32]

Duplicate of Issue #429

[3rd-Eden]

Fixed in socket.io 0.8

[thekiur]

Fixed? Windows 7 + Chrome 14 & Chrome 15 wont establish a WebSocket connection with 0.8.x, it this known?