Hi, I'm trying to make the chromium websocket client (4.0.252.0 (32473) linux) work with the websocket implementation recently added to jetty-7.
Chromium is closing the connections as soon as it gets the 101 response. The request sent was : GET / HTTP/1.1 Upgrade: WebSocket Connection: Upgrade Host: localhost:8080 Origin: http://localhost:8080 WebSocket-Protocol: testp To which Jetty responds: HTTP/1.1 101 Web Socket Protocol Handshake Upgrade: WebSocket WebSocket-Origin: http://localhost WebSocket-Location: ws://localhost:8080/ WebSocket-Protocol: testp Connection: Upgrade Chrome then closes the socket with a FIN/ACK and calls the onclose method of the websocket. Strangely if I leave out the Origin and Location headers in the response, the connection is kept open, but all messages are ignored... until jetty closes the connection at which time onclose is called by the browser. -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
