What steps will reproduce the problem?
1. Normal connect to a lazy local or online server, see 'Sec-WebSocket-Accept'
header is missing in Chrome 17
What is the expected output? What do you see instead?
Normally the client should get the "connect" state, but unfortunately it is
disconnecting immediately with status 3.
What version of the product are you using? On what operating system?
Latest one.
Please provide any additional information below.
What you need is to implement the Sec-WebSocket-Accept header, see
http://en.wikipedia.org/wiki/WebSocket#WebSocket_protocol_handshake
The client provides the key and the server respond with the encrypted accepted
header. I've patched that for you. Can I join the project? Attached the patch.
Original issue reported on code.google.com by michaelpalmer04 on 25 Apr 2014 at 8:12
Original issue reported on code.google.com by
michaelpalmer04
on 25 Apr 2014 at 8:12