Ross A. Baker
Ross A. Baker
Is this still happening on 0.19.0-M2?
Yes, that looks correct. Thanks for testing! I think this was fixed in http4s/http4s#2061. We had a blaze issue related to that, and we failed to connect the dots to...
The 501 is the default `onNonWebSocketRequest` in the `WebSocketBuilder`. The response should have a `WebSocketContext` attribute with key `org.http4s.server.websocketKey`. The `WebSocketContext` contains the `WebSocket`, that you can interact with via...
No, response. When you post to a web socket route, you get back a response with an attribute that represents the server's view of the web socket. You can then...
This is not fatal, but is unacceptably noisy. I'd still like to squash this.
A long, long time ago, nio2 didn't do as well as nio1 on benchmarks. I don't remember it being hugely different, but it's the reason that nio1 remained the default....
Note that `nio2` is gone, so the workaround is about to be gone. We'll need to do something else.
I'm glad your issue is fixed, but that still seems buggy that bad timeout configurations can lead to NPEs instead of the wrong kind of timeouts firing.
See a4040ff45e592b280c2484914172c49ec286a7b4 and https://github.com/http4s/http4s/pull/917. This is coming back somewhere, but we need to determine where.
I guess that depends on how independent you see blaze being and how much you care. I'm for whatever gets http4s on the newest blaze.