Websockets + Haproxy about aleph HOT 5 CLOSED

Netty doesn't provide an easy way to respond mid-request, so in order to support this I'm going to get a little low-level. Is this bug blocking you in some way, or is it just something you discovered?

from aleph.

At the moment it is blocking me a little bit for a web based computer game that I am making.
I can work around it by using port 10000 or some other port for websockets, but with haproxy I have a couple advantages in a production environment.
Having haproxy in front of aleph will allow me to have load balancing / failover over multiple aleph servers.
And using haproxy its possible have all the http from nginx / apache and websockets traffic over port 80 what will improve compatibility with corporate firewalls that only have port 80 open.
Haproxy can also help against abuse.
Adding haproxy support will make aleph websockets production ready :-)

from aleph.

Okay, I'll take a look at it and see exactly how much of a pain it's going to be to get this to work. My guess is that it won't be much more strange than what I'm already doing to get WebSockets and HTTP to coexist on the same port.

from aleph.

cool, thanks ! :-)

from aleph.

I've moved entirely over to Netty's implementation of WebSockets, and I'm not sure if it handles this issue properly or not (or if Haproxy has become more websocket friendly itself). If this is still an issue, you might consider talking to the Netty guys.

from aleph.