Hello Christopher,
Thanks for your research,
On Tue, Jan 11, 2022 at 6:55 PM Christopher Faulet wrote:
> Le 1/10/22 à 23:19, Willy Tarreau a écrit :
> > At this point I'm starting to think that we should probably avoid as
> > much as possible to use implicit settings for whatever is dynamic.
>
Hi,
HAProxy 2.3.17 was released on 2022/01/11. It added 51 new commits
after version 2.3.16.
This is essentially an update of 2.3 with the relevant fixes that were
collected from 2.4.9 to 2.4.12. The list below was mostly composed from
the last few 2.4 changelogs:
- using multiple log-forward
Le 1/10/22 à 23:19, Willy Tarreau a écrit :
At this point I'm starting to think that we should probably avoid as
much as possible to use implicit settings for whatever is dynamic.
Originally a lot of settings were implicit because we don't want to
have huge config lines to enforce lots of
Hi,
HAProxy 2.5.1 was released on 2022/01/11. It added 58 new commits
after version 2.5.0.
As usual, this release fixes several issues and brings some improvements:
- there was a possible slow memory leak of struct sockaddr during layer-7
retries that would end up with a redispatch. We're
Le 1/10/22 à 23:19, Willy Tarreau a écrit :
w options were still configurable on the CLI by then.
"check-ssl" has been available for a long time, so that's not the
reason behind it, but I guess you were referring to something else. I
suspect I did a dumb copy/paste from the new_server function
Hi Ilya,
> this is cleanup patch that removes default (non needed) step condition.
> behavior is not changed.
Now applied, thank you.
Willy
Hi!
Less than 24 hours between the issue opening and the fix? :-O
Great job. Really.
.marcoc
Hi,
HAProxy 2.4.12 was released on 2022/01/11. It added 2 new commits
after version 2.4.11.
The 2.4.11 introduced a major regression into the H1 multiplexer. The bug
affects all HTTP messages announcing a content length from the time there
are some contentions on the output buffer. The result
8 matches
Mail list logo