websocket problems with standard 80 port

[daralthus]

Hi,
There seems to be a problem when you use the port 80.with websockets/flashsockets in ie7/6 or chrome 6 on windows (maybe in others too..). Interesting is that it works in opera and ff!
Anyway the node terminal shows that they are connected, the client.handshake is true, however ther is no communication and it it disconnects almost imediately... a bit later a consol in ie7 shows an error about digests not matching...
Thanks for looking after it, Peter K.

[rauchg]

Are you sure the client is not trying 8080?

[daralthus]

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..

[daralthus]

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]

[aleksraiden]

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)

[daralthus]

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?)

[daralthus]

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?

[rauchg]

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

[daralthus]

Great news, thanks!