❦ 4 août 2020 14:10 +02, Bram Gillemon:
> Running debian stretch with 1.8.25-1~bpo9+1, this morning the package
> upgraded to 1.8.26-1~bpo9+1 and i started noticing some strange
> behaviour.
I have uploaded 1.8.26-2 with the upstream fix included (for all
supported distros). If you can check it
Thanks Willy,
Not to sound ungrateful at all; an updated 1.8 release with this fix would
be greatly appreciated!
On Sat, 15 Aug 2020, 19:03 Willy Tarreau, wrote:
> On Thu, Aug 13, 2020 at 08:21:28AM +0200, Erwin Schliske wrote:
> > > The patch was for the 2.0. It must be adapted for the 1.8. Bu
On Thu, Aug 13, 2020 at 08:21:28AM +0200, Erwin Schliske wrote:
> > The patch was for the 2.0. It must be adapted for the 1.8. But, it is not
> > necessary because the bug is now fixed in 2.0 and 1.8 :
> >
> > * 2.0 : http://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=307f31ec
> > * 1.8 : htt
> The patch was for the 2.0. It must be adapted for the 1.8. But, it is not
> necessary because the bug is now fixed in 2.0 and 1.8 :
>
> * 2.0 : http://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=307f31ec
> * 1.8 : http://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=179d316c
Thanks. I nee
Le 12/08/2020 à 13:00, Erwin Schliske a écrit :
Ok I confirm the issue on the 1.8 is related to the commit 6ad7cd981 and the
provided patch should fix it (on 1.8 and 2.0). But I'm unable to reproduce
the
bug on the 2.2.
I also have the problem described in this thread with the 1.8.
It would be great to know when this fix is planned to be released for the
1.8 branch, as having to have http/2 disabled (for quite a while now) is
not really a great experience.
On Wed, 12 Aug 2020, 21:00 Erwin Schliske,
wrote:
> Ok I confirm the issue on the 1.8 is related to the commit 6ad7cd9
>
> Ok I confirm the issue on the 1.8 is related to the commit 6ad7cd981 and
> the
> provided patch should fix it (on 1.8 and 2.0). But I'm unable to reproduce
> the
> bug on the 2.2.
>
I also have the problem described in this thread with the 1.8.26. When
building with the mentioned patch I get t
❦ 5 août 2020 22:48 +02, Christopher Faulet:
>> i was just setting up the 2.2 version again and i think i did
>> something wrong this morning because i can't reproduce it anymore.
>>
>> Sorry for the extra work i caused.
>>
> No problem. I always prefer a false bug report than a long fix session
Le 05/08/2020 à 22:37, Bram Gillemon a écrit :
Hi,
i was just setting up the 2.2 version again and i think i did something wrong
this morning because i can't reproduce it anymore.
Sorry for the extra work i caused.
No problem. I always prefer a false bug report than a long fix session :)
-
Hi,
i was just setting up the 2.2 version again and i think i did something wrong
this morning because i can't reproduce it anymore.
Sorry for the extra work i caused.
Kind Regards,
Bram Gillemon
> On 5 Aug 2020, at 22:05, Christopher Faulet wrote:
>
> Le 05/08/2020 à 14:52, Christopher Fa
Le 05/08/2020 à 14:52, Christopher Faulet a écrit :
Le 05/08/2020 à 12:22, Oliver Kelly a écrit :
I've opened https://github.com/haproxy/haproxy/issues/798
Here is a patch for the 1.8. Could you validate it fixes your issue ?
It fixes a bug introduced in 2.0 by the commit 6ad7cd981 ("BUG/MED
Le 05/08/2020 à 12:22, Oliver Kelly a écrit :
I've opened https://github.com/haproxy/haproxy/issues/798
Here is a patch for the 1.8. Could you validate it fixes your issue ?
It fixes a bug introduced in 2.0 by the commit 6ad7cd981 ("BUG/MEDIUM: mux-h2:
Emit an error if the response chunk for
I've opened https://github.com/haproxy/haproxy/issues/798
On Wed, Aug 5, 2020 at 7:51 PM Bram Gillemon wrote:
> I upgraded the server to the 2.2 LTS version and i have the same behaviour
> in that version.
>
> If needed i can provide a testing environment.
>
> Kind Regards,
> Bram Gillemon
>
> O
I upgraded the server to the 2.2 LTS version and i have the same behaviour in
that version.
If needed i can provide a testing environment.
Kind Regards,
Bram Gillemon
> On 5 Aug 2020, at 11:28, Oliver Kelly wrote:
>
> I too am seeing this issue with with haproxy 1.8.26-1ppa1~bionic on Ubunt
I too am seeing this issue with with haproxy 1.8.26-1ppa1~bionic on Ubuntu
18.04.4 LTS.
On Chrome (84.0.4147.105), this results in the
'net::ERR_HTTP2_PROTOCOL_ERROR 200' console error, either on the primary
page load or on load of other page resources. In Firefox (79.0), no console
errors are rep
❦ 4 août 2020 14:10 +02, Bram Gillemon:
> Running debian stretch with 1.8.25-1~bpo9+1, this morning the package
> upgraded to 1.8.26-1~bpo9+1 and i started noticing some strange
> behaviour.
For reference:
HA-Proxy version 1.8.26-1~bpo9+1 2020/08/03
Copyright 2000-2020 Willy Tarreau
Build op
Hi All,
Not sure if i hit a bug or a config problem, so before creating a bug report
i'll ask the maillinglist.
i'm running a small haproxy setup, nothing fancy yet, it's just designed so the
client can upgrade to a multi cluster setup in no time.
Running debian stretch with 1.8.25-1~bpo9+1, t
17 matches
Mail list logo
