On Fri, Feb 16, 2018 at 4:36 PM, Artur <[email protected]> wrote: > Hello, > > I have a haproxy setup with node.js application in backend. > Clients connect websockets to node.js application through haproxy and > these connections are usually established for a long time, one or more > hours. > > I wondered if there is any need to adjust default haproxy.cfg timeouts > at different levels? > As I'm here, maybe you have some other suggestions on websocket specific > setup/options tuning? > > -- > Best regards, > Artur > > > Hi,
This blog article should answer your questions: https://www.haproxy.com/fr/blog/websockets-load-balancing-with-haproxy/ That said, since the time of this article, we release the "tcp-ut" that you may want to set as well to detect faster when a client has disconnected. Note that a best practice is to implement an application layer "ping" every 1 minute and set the timeout tunnel to 61s. Baptiste
