I confirm that is the point.
In haproxy 3.0 a bug was introduced that broke hashing assumptions, the behavior will be restored, but you need to know that haproxy instance will behave differently when using code that has this bug:
1 Like