IE10 (windows 7 preview) WebSocket Error

[pleaseshutup]

In IE10's console:

WebSocket Error: Incorrect HTTP response. Status code 200, OK

[einaros]

I've verified that it works with IE 10 final on Windows 8 - so I am assuming that this is an issue with the preview build.

[pleaseshutup]

Now that IE10 is officially released on windows 7 would you mind giving it a try?

It's still busted.

SCRIPT12008: WebSocket Error: Incorrect HTTP response. Status code 200, OK

[tmpvar]

I'm seeing the same issue as @pleaseshutup

[floathybrid]

I am also seeing the same error in Windows 7 IE 10 Version: 10.0.9200.16521IS. Specifically, I am sending both text and binary messages from server and receiving on client. Chrome is able to parse okay.

[agektmr]

Hi, @einaros
I'm actually seeing the exact same issue on IE10 Windows 8 running on VirtualBox installed via ievms. The server is running on Mac OS X 10.8 which is the host of the VirualBox.

According to this information, my IE build 10.0.9200.16519 is even newer than the latest available on list and definitely not the preview build.

[einaros]

Sorry for the delay here guys; easter and all.

I am looking into it now.

[einaros]

Which versions of Node are you guys running?

[agektmr]

mine was 0.10.1.

[einaros]

Great, thanks, I'll check with that on Win8, and also pull down a Win7 image to check there.

[agektmr]

tried it on v0.8.8 as well which gives same error.

[einaros]

Strange stuff. This is what it looks like for me, on a fresh virtual install of Win7, with the latest IE10 and ws installed from npm: http://player.vimeo.com/video/63040542

[einaros]

Could someone show me a header dump of the handshake that fails?

[Sironfoot]

Same problem here. IE10 version is 10.0.9200.16521 running on Windows 7 Pro x64. I have the node.js server running on OSX, with Windows 7 running in a VM (VMware Fusion), so at first I thought it was maybe some sort of network bridge between the host & guest OS's setup by the VM fiddling with the WebSocket connection, but Chrome & Firefox running inside the Windows 7 VM work fine.

The error I get in IE10 is: "SCRIPT12008: WebSocket Error: Incorrect HTTP response. Status code 200, OK"

How do we get a header dump of a failed handshake?

[tmpvar]

Apparently there must be a trailing slash on the url when creating a WebSocket instance

Originally, I was using the following to generate a ws:// url:

var wshref = (window.location.protocol === 'https') ? 'wss' : 'ws';
wshref += '://' + window.location.host;

But I was having a hard time filtering it out of the wireshark dump.

I changed the last line above to wshref += '://' + window.location.host + '/websocket/' (also tried with /) and it now works as expected.

I tried to find the invalid handshake after getting it to work, and unless I missed something, it appears as though IE10 doesn't even bother making the request unless there is a trailing slash.

[Sironfoot]

OK, this is weird. I tried tmpvar's suggestion. IE10 seems to insist on something being added after the trailing slash, so...

ws://localhost:3000

...doesn't work, neither does...

ws://localhost:3000/

...(note the trailing slash), but...

ws://localhost:3000/xxx

...does work.

[pleaseshutup]

I have the same results as @Sironfoot

[floathybrid]

Yup, Sironfoot's workaround is working for me too: trailing slash + characters.

[einaros]

Weird stuff. Strange that I didn't see this behaviour when I tested with IE10. I did my testing on Win8, though - did all of you with problems use Win7?

[tmpvar]

yeah

[pleaseshutup]

Yes IE10 on windows 7

[lpinca]

Closing this as it seems that the issue is in IE10 and not in this library.