Hi Benjamin, On Tue, Dec 18, 2012 at 10:36:59AM -0500, Benjamin Polidore wrote: > I get this when the session disconnects: > > Dec 18 07:16:40 localhost haproxy[28357]: > 10.0.77.83:58914[18/Dec/2012:07:10:12.899] http-in~ app_back/s1 > 72/0/69/70/387465 101 > 60777735 - - ---- 1/1/0/0/0 0/0 "GET / > socket.io/1/websocket/qXV9FijWB_XXVl5tci5m HTTP/1.1"
Just out of curiosity, would you like to test snapshot 20121220 when it's out ? If your server's timeout is shorter than haproxy's (which I hope it is), it is possible that it closes because it doesn't see anything anymore and haproxy is then unable to detect a timeout itself. This could happen because the bug affecting POST requests that we just fixed is in fact related to data upload. If your websocket connection receives many data from the client, it is possible that you've been hit by the same issue. Regards, Willy
