"websocket connection invalid" on Chromium nightlies

[toji]

It looks like the recent Chromium and Chrome Canary builds may have changed the Websocket protocol again or something related. Attempts to establish a websocket connection cause the server to print out "websocket connection invalid" and it attempts to fall back to other methods.

This behavior is present in Chromium 16.0.906.0 (Developer Build 105111 Mac OS X) and Chrome 16.0.911.1 Canary. Probably a few versions back as well.

Chrome 16.0.904.0 Dev does not demonstrate this problem.

[3rd-Eden]

Are you using Socket.IO 0.8.5 as we landed hybi-16 support there for Chrome 16 support.

[toji]

Right, sorry. I have a couple of instances of Socket.io on my machine, was looking at the wrong one.

Updated to 0.8.5 and it's fixed.