17644 2012-06-28 23:46:58 +0000 OK I spent hours all over the web and your docs getting to grips with websocket, my question now is this.... in the the handshake....how does one actually implement the header for the websocket? there is not explanation of this anywhere... how is the head 2012-06-29 08:04:18 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified Other other RESOLVED INVALID http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian bugs mike public-webapps public-webapps-bugzilla oldest_to_newest 69520 0 contributor 2012-06-28 23:46:58 +0000 Specification: http://www.w3.org/TR/websockets/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: OK I spent hours all over the web and your docs getting to grips with websocket, my question now is this.... in the the handshake....how does one actually implement the header for the websocket? there is not explanation of this anywhere... how is the header constructed in either php or javascript for the websocket handshake for the example like: GET /chat HTTP/1.1 Host: server.example.com Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ== Origin: http://example.com Sec-WebSocket-Protocol: chat, superchat Sec-WebSocket-Version: 13 Because during my test...I in chrome I see the error: Error during WebSocket handshake: 'Sec-WebSocket-Accept' header is missing in the server it keeps disconnecting...I am testing locally in xampp...and and enabled the websocket that works with like: php -q C:\xampp\htdocs\server\server.php but it disconnects and the chrome console shows: Error during WebSocket handshake: 'Sec-WebSocket-Accept' header is missing Can I see an example of how to actually send the headers and the Sec-WebSocket-Key in when we send the handshake? Posted from: 87.114.223.140 User agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5 69529 1 bugs 2012-06-29 08:04:18 +0000 Protocol is defined in the IETF spec.