Websocket in pending state ...

[reda]

Hi,

I'm enable to get websocket working on Chrome/Win XP through socket.io

The app is hosted on nodester and it works with my Chrome/Debian Lenny
(5.0)

The socket is hanging on the pending state.

See the screenshot: https://picasaweb.google.com/reda.abdi/Websockets#5602683866177911858

Why is it hanging? Why it never get it 101 status from response
handshake

I delete the socketio cookie / refresh and I have deliberately asked
socket io not to try another transport:

var options = {
rememberTransport: false,
tryTransportsOnConnectTimeout: false
};

socket = new io.Socket(node_server_url, options);
socket.connect();

If I remove options , it falls back to the so inefficient xhr-polling.

Thanks for your help.

[Jukka-Pekka Kekkonen]

Try turning off your firewall + anti-virus software if you have any

[DRE]

Anybody doing anything interesting to detect this state and message the user?

On Tue, May 10, 2011 at 3:29 AM, Jukka-Pekka Kekkonen <karat...@gmail.com> wrote:

Try turning off your firewall + anti-virus software if you have any

--
DRE
http://www.itestcars.com
http://dre.lightswit.ch

[reda]

Thanks Jukka-Pekka Kekkonen. It was a firewall issue

Since I posted this thread 6 days ago I figured out that Avast
Antiivirus blocked all websocket communications. If I stop the web
agent, websockets start working.
I tried creating an exception in Avast, but it doesn't work. Avast
sucks.

I removed tryTransportsOnConnectTimeout: false from my options
arguments, and socket.io is falling back to xhr-polling and works fine
even if there is some disconnections some times and I need to deal
with that in the client side (reconnect each time disconnection
happens), and it is quite easy to handle.

Now, I have a problem with the same origin policy in Chrome/
websockets. Why Chrome throws this error when the page loads from
domain.com and the websocket connects to comet.domain.com ? Isn't it
the same domain? What security risk is there?

How could I still serve my website from my old server, and running
websocket on nodejs server hosted on nodester for example?





On May 10, 11:29 am, Jukka-Pekka Kekkonen <karatepe...@gmail.com>
wrote: