Created
January 7, 2012 00:59
-
-
Save robertjd/1573310 to your computer and use it in GitHub Desktop.
Websocket Handshake without Upgrade header
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hybi-07-12, headers: { host: 'example.com', | |
'sec-websocket-key': 'jjtFcDA0FonXscXj25UuaQ==', | |
'sec-websocket-origin': 'ws://example.com/socket.io/1/websocket/1105054216814116754', | |
'sec-websocket-version': '8', | |
'sec-websocket-protocol': '8', | |
'cache-control': 'max-stale=0', | |
connection: 'Keep-Alive', | |
'x-bluecoat-via': 'DDBD0991AB5F8902' } |
Hey did you ever figure out how to deal with this?
Seems like those orwellian fucks at Blue Coat don't support websockets at all, so even if you did do the handshake with that request, you'd just end up with opcode -1 no matter what.
Seems like web sockets are supported in newish versions of Blue Coat Proxy SG: http://bluecoat.force.com/knowledgebase/articles/Solution/WebSocketsupportintroducedinSGOS6552PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is what our websocket handhakes are looking like when they come from a particular client that is behind a Blue Coat proxy