Unable to get websockets working with http4s example

[dcapwell]

I am running the sample from https://github.com/http4s/http4s/blob/develop/examples/src/main/scala/org/http4s/examples/blaze/BlazeWebSocketExample.scala and trying to upgrade to ws. It seems that the handshake doesn't work as expected, nor can I get a javascript example to talk to the endpoint.

Here is the test (control):

$ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: echo.websocket.org" -H "Origin: http://www.websocket.org" http://echo.websocket.org
HTTP/1.1 101 Web Socket Protocol Handshake
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: content-type
Access-Control-Allow-Headers: authorization
Access-Control-Allow-Headers: x-websocket-extensions
Access-Control-Allow-Headers: x-websocket-version
Access-Control-Allow-Headers: x-websocket-protocol
Access-Control-Allow-Origin: http://www.websocket.org
Connection: Upgrade
Date: Tue, 22 Apr 2014 17:52:24 GMT
Server: Kaazing Gateway
Upgrade: WebSocket
WebSocket-Location: ws://echo.websocket.org/
WebSocket-Origin: http://www.websocket.org

^C

$ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: html5rocks.websocket.org" -H "Origin: http://www.websocket.org" http://html5rocks.websocket.org/echo
HTTP/1.1 101 Web Socket Protocol Handshake
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: content-type
Access-Control-Allow-Headers: authorization
Access-Control-Allow-Headers: x-websocket-extensions
Access-Control-Allow-Headers: x-websocket-version
Access-Control-Allow-Headers: x-websocket-protocol
Access-Control-Allow-Origin: http://www.websocket.org
Connection: Upgrade
Date: Tue, 22 Apr 2014 17:55:03 GMT
Server: Kaazing Gateway
Upgrade: WebSocket
WebSocket-Location: ws://html5rocks.websocket.org/echo
WebSocket-Origin: http://www.websocket.org

^C

I now try the same curl with the endpoint power by blaze:

$ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost" -H "Origin: http://www.websocket.org" http://localhost:8080/http4s/ws
HTTP/1.1 400 Bad Request
Content-Length: 28
Connection: close

Bad Websocket Version header

Ok, so let me add the version and key (I would expect the server to reply with what version it supports: https://tools.ietf.org/html/rfc6455#section-11.3.5)

$ curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost" -H "Origin: http://www.websocket.org" -H "Sec-WebSocket-Version: 13" -H 'Sec-WebSocket-Key: +onQ3ZxjWlkNa0na6ydhNg==' http://localhost:8080/http4s/ws
^C

Not getting back the handshake headers, but the connection is made, so now trying from javascript. There is a simple example found here: http://www.websocket.org/echo.html. When I put ws://localhost:8080/http4s/ws and try to connect, I see that the connection is still pending in chrome, client never sees that the connection is "connected". Trying the two control endpoints above work as expected.

[bryce-anderson]

Sorry for the slow reply, I didn't get a notification. The websocket support is certainly a work in progress which has take lower priority than stabilizing the http parser and NIO backends. I've been using chrome browsers to test websockets and the , and I hear that firefox isn't working so there is a good chance I've done something very version specific. I'm hoping to have a bit of time this weekend to hit some soar spots in here so I'll add this to the list.

[bryce-anderson]

This issue was partially addressed with commit f9d0738. Further investigation to all problems still pending.

[javadba]

Hi - 2.5 years later. Is Websockets working with http4s?

[rossabaker]

Only on the blaze-server (no clients, no server backends), but yes. There is a runnable example.