Hi,

> Hello everyone, 
> 
> Is there a release date for haproxy 1.5 stable version ? 
> 
> Regarding this list: http://haproxy.1wt.eu/knownbugs-1.3.html , 1.5.22
> is bug free, does anyone here has a feedback about 1.5.22 in production
> environment ?

The is no ETA.


This is a list for bugs for the 1.3 branch, last updated in 2009. Its
completely obsolete.


Known bugs in dev22, but fixed in git are:

$ git log --oneline v1.5-dev22..master | grep BUG
25a1522 BUG/MINOR: reject malformed HTTP/0.9 requests
f6c22c8 BUG/MEDIUM: pattern: fix wrong definition of the pat_prune_fcts array
e5978bf BUG/MEDIUM: acl: boolean only matches were broken by recent changes
d048d8b BUG/MINOR: http: fix encoding of samples used in http headers
80a92c0 BUG/MEDIUM: http: don't start to forward request data before the connect
da5d4a5 BUG/MINOR: log: The log of quotted capture header has been terminated 
by 2 quotes.
338a031 BUG/MEDIUM: map: The map parser includes blank lines.
4a4e6bc BUG/MEDIUM: compression: fix the output type of the compressor name
0724903 BUG/MINOR: raw_sock: also consider ENOTCONN in addition to EAGAIN for 
recv()
5830213 BUG/MINOR: config: fix a crash on startup when a disabled backend 
references a peer
3634624 BUG/MEDIUM: http: continue to emit 503 on keep-alive to different server
2481d16 BUG/MEDIUM: backend: prefer-last-server breaks redispatch
abd03df BUG/MINOR: config: server on-marked-* statement is ignored in 
default-server
518cedd BUG/MEDIUM: ssl: always send a full buffer after EAGAIN
07ba08b BUG/MINOR: ssl: fix syntax in config error message
5498472 BUG/MEDIUM: config: immediately abort if peers section has no name
9a60ff9 BUG/MEDIUM: peers: fix key consistency for integer stick tables
8f39dcd BUG/MINOR: channel: initialize xfer_small/xfer_large on new buffers
852745d BUG/MAJOR: check: fix memory leak in "tcp-check connect" over SSL
f522f3d BUG/MEDIUM: stats: the "lastsess" field must appear last in the CSV.
3be293f BUG/MEDIUM: checks: immediately report a connection success
f621bea BUG/MINOR: tcpcheck connect wrong behavior





Regards,

Lukas                                     

Reply via email to