Hi, On Sat, Feb 11, 2017 at 12:31 AM, Markus Rathgeb <[email protected]> wrote: > This seems to be working as expected. > > But it seems to fail for WebSockets. > I don't know how to start and how to fix that. > Is this something to configure? > Do I need to overwrite some methods?
AsyncProxyServlet handles HTTP only. You would need to write a WebSocket proxy, which we have not done in Jetty. The idea would be to use a standard WebSocket endpoint on the server; when that endpoint starts receiving WebSocket frames, you will use a WebSocket client to forward them to the right backend. What you describe is basically a simple load balancer. As such an alternative solution could be using HAProxy. If choosing the backend is done with a simple logic, perhaps it's a better solution. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
