Status of HAProxy's known bugs per version (as of 2009/10/18)

I have noticed that there are still quite a lot of people running old versions which contain important bugs they're not aware of. Sometimes they even send bug reports while a fixed version has been available for months.

This matrix is there to help these people discover what issue might affect them on the version they are running. It only covers stable branch 1.3 starting from 1.3.14.

Bugs are classified by low to high importance, low implying minor inconvenience, medium implying unexpected behaviour and high meaning a risk of service disruption.

An 'X' in a column indicates the bug affects that version with no known easy workaround. A 'W' indicates that the bug is present but a reasonable workaround is possible. An 'S' indicates a sleeping bug which could not be triggered under known conditions but which could have with minor unrelated code changes, so it might possibly affect some patched versions.

(M) transparent proxy address ignored in backendX
(M) hot reconfiguration failed because of a wrong error checkX
(L) stats report wrong number of connectionsXX
(L) server might not exist when sending error reportXX
(M) tproxy uses wrong sourceXX
(M) overlapping server flagsXX
(L) wrong byte count loggedXX
(M) sepoll truncates dataXX
(L) failed conns counted in the frontendXXX
(M) appsession lookup in URL does not workXXX
(L) server connections and retries counted wrongXXX
(L) option allbackups not working anymoreXXX
(M) stats output limited to 16 kBXXXX
(M) stats output sometimes truncatedXXXXX X
(M) risk of event starvation in sepollXXXXX X
(M) scheduler causes random delaysXXXXXX XX
(M) requests can stall in the backend queueXXXXXX XX
(L) use_backend would not correctly consider "unless"WWWWWWW WWW
(H) segfault on url_param + check_post WWW
(M) server timeout could be ignoredXXXXXXX XXX
(M) sepoll causes busy loopsXXXXXXX XXX
(H) regparm is broken on GCC < 3XXXXXXX XXX
(M) maxconn not respected on serversXX XX
(M) connection throttling could return 0 connsWWWWWWWW WWWW
(M) configuration reload fails on backendsWWWWWWWWW WWWWW
(M) configuration reload fails on disabled proxiesWWWWWWWWW WWWWW
(L) ACL segfaults in default sectionWWWWWWWWW WWWWW
(L) cookie capture ignores responsesXXXXXXXXXX XXXXXX
(L) fatal startup errors not displayed in daemon modeXXXXXXXXXXX XXXXXXX
(M) dead servers draining pending connectionsXXXXXXXXXXX XXXXXXX
(L) listen does not accept more than 2 ip:port couplesWWWWWWWWWWWW WWWWWWWW
(M) server state tracking can take ages to converge WWWWWWWW
(M) option "transparent" not working with backendsWWWWWWWWWWWW WWWWWWWW
(L) startup exits on bind warningsXXXXXXXXXXXX XXXXXXXX
(L) source keyword causes issues in defaults sectionWWWWWWWWWWWW WWWWWWWW
(M) wrong maxconn test during accept causes error messagesWWWWWWWWWWWWW WWWWWWWWW
(M) busy loops randomly occuring in 1.3.16 <