websocket problems with standard 80 port about socket.io HOT 8 CLOSED

Are you sure the client is not trying 8080?

from socket.io.

Yes, of course! (I tried now with the port option explicitly setted 80. It's the same.. ff working, ie not..) You can try out with the example just set the server to listen on 80 and the client to 80 too then use ie7 etc..

from socket.io.

Here's the ie7 firebug lite log I am actually talking about:
[WebSocket] policy file: xmlsocket://donat.io:843[WebSocket] connected [WebSocket] request header: GET /socket.io/flashsocket HTTP/1.1 Upgrade: WebSocket Connection: Upgrade Host: donat.io Origin: http://donat.io Cookie: Sec-WebSocket-Key1: l9175 5 2 .> 3 40 Sec-WebSocket-Key2: uj26378 Y12 G81.6 [WebSocket] sent key3: t×�;qã�÷[WebSocket] response header: HTTP/1.1 101 WebSocket Protocol Handshake Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Origin: http://donat.io Sec-WebSocket-Location: ws://donat.io/socket.io/flashsocket [WebSocket] reply digest: 5��[Aë2-�º;©Å�º_[WebSocket] digest doesn't match: 5��[Aë2-�º;©Å�º_ != �1Å�Ö;1b\�^÷3­�À[WebSocket] close [object Error]

from socket.io.

Maybe firewall or proxy? At normal, WS is not typically HTTP traffic, and good idea is going to 443 (SSL default) using port, becouse most of all network device, who detected and filtering traffic, granted arbitrary TCP traffic at SSL port (see only to first data - handshake and enabled all other traffic without block or recognize)

from socket.io.

nah, I don't think so. 80 used to be open everywhere and I don't use any proxies, and why would it work on some specific browsers then? I will try ssl later but could you please be so kind to try to reconstruct the bug? (just use 80 with your example, and for example ie7) I will look into it deeper when I have some time...
Thanks!
(Btw, is there any option on the server side for a more detailed log?)

from socket.io.

Of course you were right, it is an is issue with avast antivirus... https is not a real option for me cuz mixed data warnings and other such.. do you have some advise to me?

from socket.io.

Socket.IO will soon try different transports when one fails, so that problem will be likely averted.

from socket.io.

Great news, thanks!

from socket.io.