Socket.IO and Windows Chrome Stuck

[pyrostrex]

It stucks at "client Authorized for"

[3rd-Eden]

Please provide us with more information, like a reproduceable test case, version numbers etc

[pyrostrex]

Chrome Version, 12.xx.xxx.xxx (Latest). I don't have any test case sorry. Will try to test again. Maybe there is something wrong with my code :P.

Edit : Socket.io git cloned from master.

[3rd-Eden]

Is it still reproducible with the current master?

[pyrostrex]

Yep.

[3rd-Eden]

How can we reproduce it? As I tried to do so, but I'm unable.

[pyrostrex]

Maybe there's some problem with my javascript coding. But weird thing is mac chrome, firefox doesn't have any problem. only with Windows chrome this problem raised.

[pyrostrex]

So... I tried with the chat example. It doesn't work either. Socket.io only problematic when using windows 7 chrome. I tried to use mac os x chrome and it works just fine. I think it's just chrome? Btw, I'm using the latest chrome. Updated before testing the chat example.

[emilingerslev]

I also have the problem with chrome on windows 7. Any news on this?

[takempf]

Is it safe to assume we're all using the latest developer version of Chrome here? 14.0.835.8 (dev-m) fails to connect properly. The error server side is "warn - websocket connection invalid"

[jaypeeZero]

@Fauntleroy : Are you running this locally or on a server? If on a server, which server is it? I have found problems with Heroku and some of the sockets, for example they don't even allow WebSockets to be used.

Try adding other transports like flashsocket and xhr-polling and remove websocket and see if that fixes your problem.

[luksm]

This is happening here also, i'm using the last stable version available (12.0.742.122) and I'm getting the same error on the server side as Fauntleroy. Tried running it locally and on 2 different servers (both managed by me - Debian & Ubuntu) and it fails....

[andreabat]

Hello after chrome update to 14.0.835.8 dev on linux, I get "warn - websocket connection invalid". It worked perfectly before the update.
Running on same box ( server and chrome).

[takempf]

For those of you having a problem like mine, the newest version of Chrome is using a new version of websockets and will be fixed in due time: #429

[pyrostrex]

@3rd-Eden, I do some tests today, and found out that when I use a (windows 2008 r2 US server) and use chrome to try connecting to socket.io. It turned out that it works (this I think is the reason you unable to reproduce). I think it had to do with the connection speed? or the IPs group? our connection speed in malaysia is only 128kbps maximum (using accelerator). so I think by using google chrome we can only get up to 20kbps? Chrome version is 13.xx.xx.xx (latest).

[pyrostrex]

@guille, @3rd-Eden, I think that this problem will not be fixed in a long time so as for that. I will be closing it as I found out that removing websocket from the list of transports solve my problem. Thus, thank you for trying to help me.