Websockets transport broken in Chrome about socket.io

[mscdex]

Hmmm... what version of Chrome/Chromium are you using? I'm using Chromium (Win32) 6.0.397.0 (46553) with no problems when using WebSockets.

[mscdex]

I am unable to access that link (I get "Connection refused"). I'm curious though, is your socket.io server running on a different domain or port number than your web server that's hosting the socket.io client? If so, maybe there is a cross-domain issue occurring somehow?

EDIT: Looks like you removed your comment before I replied... but the question still stands :-)

[rauchg]

0.1.94 changed the way to handle the Upgrade header, I'm going to adapt it soon. For now, you'll have to use .93.

[msokk]

Thanks!, .93 works

I observe the same behavior with chromium 6.0.416.0 (48140) on Debian.
$ node -v
v0.1.93-5-g8d1f118

[mscdex]

@substack: The newest versions of Chromium implement a newer and different draft of the websockets specification that socket.io currently does not support. This new draft uses different headers and incorporates a new security mechanism. I've made the necessary changes to my socket.io fork to accommodate both recent drafts (the older 75 and the newer 76) of the websocket spec. Also, node v0.1.97 was just released the other day.