On Wed, Jun 03, 2020 at 12:20:15PM +0200, William Dauchy wrote:
> Hello Arthur,
>
> On Wed, Jun 3, 2020 at 11:38 AM Artur wrote:
> > What is the risk to trigger this bug in real life ? How to avoid it
> > before the next haproxy release ?
> > In my setup haproxy 2.1.5 has threads enabled by defau
Hello Arthur,
On Wed, Jun 3, 2020 at 11:38 AM Artur wrote:
> What is the risk to trigger this bug in real life ? How to avoid it
> before the next haproxy release ?
> In my setup haproxy 2.1.5 has threads enabled by default (Debian Buster
> backports).
You will trigger this issue if you are in t
Hello,
What is the risk to trigger this bug in real life ? How to avoid it
before the next haproxy release ?
In my setup haproxy 2.1.5 has threads enabled by default (Debian Buster
backports).
Le 02/06/2020 à 19:28, William Dauchy a écrit :
> On Tue, Jun 2, 2020 at 12:13 PM William Dauchy wrote:
On Tue, Jun 2, 2020 at 12:13 PM William Dauchy wrote:
> it seems like I broke something with this commit, but I did not have
> it in v2.2
small followup:
Sorry for that one, the backport was not exactly as I thought, and so
no test were done before release outside of 2.2 branch:
- a small mistake
On Fri, May 29, 2020 at 4:31 PM William Lallemand
wrote:
> William Dauchy fixed the connection idle cleanup upon a server maintenance or
> an ip/port change.
> BUG/MEDIUM: connections: force connections cleanup on server changes
it seems like I broke something with this commit, but I did no
Hi,
HAProxy 2.1.5 was released on 2020/05/29. It added 90 new commits
after version 2.1.4.
This version reverts some fixes about the Proxy Protocol introduced in 2.1.4,
unfortunately these fixes broke softwares that weren't following correctly the
Proxy Protocol specification.
The "http-check se
6 matches
Mail list logo
