1
Vote

Handshake isn't working

description

I have a feeling this has something to do with sockets not being closed or something deep in the TCP protocol, but am not sure - could use some help on this one.
 
See attached file to see what's happening. Basically the handshake is only completing about 20% of the time (or less).
 
Get latest then open the solution in the Trunk folder.

file attachments

comments

coolpablo wrote Dec 27, 2011 at 4:15 PM

Here is a screenshot of a successful handshake (packets captured from the wire).

wrote Dec 27, 2011 at 5:37 PM

coolpablo wrote Dec 27, 2011 at 5:37 PM

Attached a screenshot of a request that didn't get a handshake.

wrote Dec 27, 2011 at 5:59 PM

coolpablo wrote Dec 27, 2011 at 5:59 PM

Added a diff screenshot between MF and JS client requests.

coolpablo wrote Dec 28, 2011 at 3:37 AM

This one works:

GET /app/de39425369c0ebdccb7e?client=js&version=1.8.5 HTTP/1.1
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Key2: 1 0 IA DM j2
Host: ws.pusherapp.com
Sec-WebSocket-Key1: _411M 01h\3 40
Origin: ws.pusherapp.com

0s`VN1 3



But this one won't work:

GET /app/de39425369c0ebdccb7e?client=js&version=1.8.5 HTTP/1.1
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Key2: 0840166p0 C y0
Host: ws.pusherapp.com
Sec-WebSocket-Key1: T O1 0 O1
Origin: ws.pusherapp.com

2iQO G8

juliusfriedman wrote Dec 28, 2011 at 10:19 PM

Thank you for the information!

I have sent an email to Paul reguarding my thoughts on the matter, we will need to investigate further however I believe this other Framework issue may provide us with the "missing details"

http://netmf.codeplex.com/workitem/1321

If not and there is something else running a muck then we will just need to investigate further. Thank you for the information again and we will respond as soon as we can quantify what exactly is the culprit!

wrote Feb 13, 2013 at 7:31 PM