Hi,
HAProxy 1.8.22 was released on 2019/10/25. It added 46 new commits
after version 1.8.21.
The main issue addressed in this release is an occasional risk of crash in
H2 on skipped frames. The other issues are less important, and were already
addressed in 1.9 and 2.0 released since last August.
Hi,
HAProxy 1.7.12 was released on 2019/10/25. It added 114 new commits
after version 1.7.11.
I noticed that due to the vast majority of the recent bugs being related
to modern changes like threads, muxes, connection scheduling etc, very
few fixes affect older versions like 1.7 and 1.6 and we ten
Hi,
HAProxy 1.6.15 was released on 2019/10/25. It added 109 new commits
after version 1.6.14.
These are essentially the same fixes that went into 1.7.12 (as I said in
the other thread, 1.6 and 1.7 were very similar). The last 1.6 was even
3 months older than the latest 1.7, so it's about time to
Hi all,
I'm just wondering what to do with 1.5. I've checked and it didn't
receive any fix in almost 3 years. The ones recently merged into 1.6
that were possible candidates for 1.5 were not critical enough to
warrant a new release for a long time.
Now I'm wondering, is anyone interested in this
Hi Brian,
On Thu, Oct 24, 2019 at 05:10:40PM +, Brian Diekelman wrote:
> Thank you for turning that around so quickly, Willy.
>
> We'll pull down the new release when it's available.
So just FYI, 1.8.22 was released with the fix.
Cheers,
Willy
Hello,
I know I'm reporting an issue with an old version, but I got 2 segfaults
in 48h.
As I only got 3 segfaults with HAProxy in +10 years, I just wanted to make
sure these bugs have been caught and are now fixed.
haproxy -vv output:
HA-Proxy version 1.9.6 2019/03/29 - https://haproxy.org/
Bui
Hello,
I'm rewriting a complex HAProxy config file and would like to be sure how
ssl-default-bind-options and bind options work together.
I would like to configure safe options by default, but still allow
less-safe protocols on some frontend. I'm puzzled by "force-X"
documentation (does it really
Hello,
Patch attached. Adding an option "http-check send-name-header ".
It adds a header per server in healthchecks, similar usage to
"http-send-name-header". Built and tested locally.
frontend myfrontend
bind *:8080
mode http
default_backend mybackend
backend mybackend
mode ht
Hi,
HAProxy 2.1-dev3 was released on 2019/10/25. It added 155 new commits
after version 2.1-dev2.
It's two weeks later than initially expected due to being diverted by bugs
but the main point is that we're converging towards something better :-)
So now we've finally merged the tail of pending fe
Hi Olivier,
As far as I can remember, 1.9 had a series of segfaults involving H2 and HTX,
patched from release to release.
[ http://www.haproxy.org/bugs/bugs-1.9.6.html |
http://www.haproxy.org/bugs/bugs-1.9.6.html ]
As a rule of thumb, I can only suggest you try with the latest 1.9 release
Hi,
add a second patch to address ca-list case.
++
Manu
> Le 24 oct. 2019 à 12:14, Emmanuel Hocdet a écrit :
>
> Hi,
>
> Little patch with big win when ca-file is used in server line.
>
> ++
> Manu
>
> <0001-MINOR-ssl-deduplicate-ca-file.patch>
>
0001-MINOR-ssl-deduplicate-ca-file.patch
I'm trying to find out what the default values are for the following
parameters for HAproxy 1.5:
timeout client
timeout server
timeout tunnel
Where can I find the values? -- I don't seem to be able to find them in
the documentation at
https://cbonte.github.io/haproxy-dconv/1.5/configuration.ht
Hi,
Le 25/10/2019 à 22:28, Troels Arvin a écrit :
I'm trying to find out what the default values are for the following
parameters for HAproxy 1.5:
timeout client
timeout server
timeout tunnel
Where can I find the values? -- I don't seem to be able to find them in
the documentation at
https://c
On Fri, Oct 25, 2019 at 04:54:44PM +0200, GARDAIS Ionel wrote:
> Hi Olivier,
>
> As far as I can remember, 1.9 had a series of segfaults involving H2 and HTX,
> patched from release to release.
> [ http://www.haproxy.org/bugs/bugs-1.9.6.html |
> http://www.haproxy.org/bugs/bugs-1.9.6.html ]
>
15 matches
Mail list logo