mirror of
http://git.haproxy.org/git/haproxy.git
synced 2026-02-07 03:33:17 +02:00
5f4fe20116
The warn-blocked-traffic-after can be significantly lowered. In any case, in order to be usable it must be well below the limit to have a chance to emit exploitable traces before the watchdog finally fires. Even configured at 1ms it looks very difficult to trigger it on a laptop doing SSL and compression, so applying a 100-fold factor to cover for large configs and small machines sounds sane for 3.1. In any case, even at 100ms, the service degradation becomes quite visible.
