We have noticed our idle websocket connections closing too early in 1.7.2.
In 1.6.11, this works fine. We use a configuration very similar to the second “advanced” configuration in http://blog.haproxy.com/2012/11/07/websockets-load-balancing-with-haproxy/.
Idle WebSocket connections are always terminated after the shorter of “timeout client” or “timeout server”. If a shorter “timeout server” or “timeout client” is set in the websocket backend, it is respected, but a longer one is not. Explicitly setting “timeout tunnel” or “option http-tunnel” in the websocket backend has no effect.
The same configuration in 1.6.11 has no such issue.