socket.io issue with Chrome 14

[ghost]

Hi,

I'm having some issue with Chrome 14.0.835.163, when a client tries to connect I get this error on the server:

19 Sep 16:10:51 - Initializing client with transport "websocket"
19 Sep 16:10:51 - WebSocket connection invalid or Origin not verified

on the client this error:

WebSocket is closed before the connection is established.

According to other posts switching to socket.io 0.8 or higher may solve this issue. Is it planned any time soon or is there a solution to temporary fixed it?

Thanks for your help and great work! Bastien

[ncavig]

I'm having the same issue as well. Seems like a full update of all socketio code still produces poor results with chrome. I've got it working with Safari. Anyone else have any insight?

[rauchg]

Please upgrade to 0.8. Should upgrade cleanly without issues.

[MichaelWhi]

Hi, I don't know if it is related or a new bug... I also experienced errors with Chrome, making Juggernaut crash completely during connecting a WebSocket in Chrome. However, I found the same error in the socket.io Tracker at https://github.com/LearnBoost/socket.io/issues/602, which they fixed in Version 0.8.7.

So - I am running Juggernaut on Heroku - I just had to change the line 18 in package.json to:

{ "socket.io" : "=0.8.7"

I did not run your tests, but the app performs well in every browser, so this really seemed to fix it. I'd recommend you to update the package.json in this repo accordingly. And: Thanks a lot for this awesome piece of software!

[kevzettler]

I am having this same problem. I believe this was fixed in this merge:

https://github.com/maccman/juggernaut/pull/113

am I safe to say that upgrading juggernaut should fix this now?

[MichaelWhi]

I'd say yes - that's the change I proposed and I've been running juggernaut with socket.io 087 since then (end november or so) without problems on our production system.