On Fri, Apr 3, 2020 at 5:21 AM Igor Cicimov
wrote:
> Hi all,
>
> Probably another quite basic question that I can't find an example of in
> the docs (at least as a warning not to do that as it does not make sense or
> bad practise) or on the net. It is regarding the usage of multiple balance
> st
Hi all,
Probably another quite basic question that I can't find an example of in
the docs (at least as a warning not to do that as it does not make sense or
bad practise) or on the net. It is regarding the usage of multiple balance
statements in a backend like this:
balance leastconn
bala
Hello,
after updating HAProxy from 2.1.13 to 2.1.14 the TCP check with my
dovecot setup doesn't work anymore. Nothing changed except the update.
In dovecot I get the following errors:
> Apr 03 00:21:28 srv1 dovecot[1378]: submission-login: Error:
> haproxy(v2): Client disconnected: Invalid TLV:
Hello,
patch is urgent.
openssl has changed download path, I guess it was done in purpose (to
signal people that they download outdated openssl)
so ... we need to upgrade to 1.1.1f
Cheers,
Ilya Shipitcin
From a21479ae91ad2c43dbe14d7d119eedc2363e0f49 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
I reverted that commit, but it doesn't appear to have fixed the issue.
I also tried adding a stick-table using this peers group to my config (this
test cluster didn't actually have any stick-tables), but it still fails at
startup with the same error.
On Thu, Apr 2, 2020 at 11:28 AM Tim Düsterhus
Hello,
this PR cleans up SSL linking.
it is very well aligned to "how to link to custom openssl" documentation.
Cheers,
Ilya Shipitcin
From 8fd3b9165558c4d0e3bc837df1ba8caca67ed059 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 2 Apr 2020 23:34:47 +0500
Subject: [PATCH] CI: use better
James,
Am 02.04.20 um 19:53 schrieb James Brown:
> I'm upgrading one of our test clusters from 2.0.13 to 2.0.14 and our
> regular graceful-restart process is failing with:
>
> [ALERT] 092/174647 (114374) : [/usr/sbin/haproxy.main()] Some protocols
> failed to start their listeners! Exiting.
I su
I'm upgrading one of our test clusters from 2.0.13 to 2.0.14 and our
regular graceful-restart process is failing with:
[ALERT] 092/174647 (114374) : [/usr/sbin/haproxy.main()] Some protocols
failed to start their listeners! Exiting.
Looking at strace, it looks like the bind(2) call for the peer s
On 02 Apr 15:27, Julien Pivotto wrote:
> On 02 Apr 15:03, Willy Tarreau wrote:
> > Hi,
> >
> > HAProxy 2.1.4 was released on 2020/04/02. It added 99 new commits
> > after version 2.1.3.
> >
> > The main driver for this release is that it contains a fix for a serious
> > vulnerability that was res
On Thu, Apr 02, 2020 at 03:27:07PM +0200, Julien Pivotto wrote:
> On 02 Apr 15:03, Willy Tarreau wrote:
> > Hi,
> >
> > HAProxy 2.1.4 was released on 2020/04/02. It added 99 new commits
> > after version 2.1.3.
> >
> > The main driver for this release is that it contains a fix for a serious
> > v
On Thu, Apr 02, 2020 at 03:27:26PM +0500, ??? wrote:
> Hello,
>
> ongoing typo fixes.
Merged, thanks!
Willy
On 02 Apr 15:03, Willy Tarreau wrote:
> Hi,
>
> HAProxy 2.1.4 was released on 2020/04/02. It added 99 new commits
> after version 2.1.3.
>
> The main driver for this release is that it contains a fix for a serious
> vulnerability that was responsibly reported last week by Felix Wilhelm
> from Goo
On Thu, Apr 02, 2020 at 03:26:31PM +0500, ??? wrote:
> forgot to attach a ptach itself ))
Normally this tradition is reserved to me :-)
Now applied, thank you Ilya!
Willy
Hi,
HAProxy 1.8.25 was released on 2020/04/02. It added 37 new commits
after version 1.8.24.
The main driver for this release is that it contains a fix for a serious
vulnerability that was responsibly reported last week by Felix Wilhelm
from Google Project Zero, affecting the HPACK decoder used f
Hi,
HAProxy 1.9.15 was released on 2020/04/02. It added 53 new commits
after version 1.9.14.
The main driver for this release is that it contains a fix for a serious
vulnerability that was responsibly reported last week by Felix Wilhelm
from Google Project Zero, affecting the HPACK decoder used f
Hi,
HAProxy 2.0.14 was released on 2020/04/02. It added 86 new commits
after version 2.0.13.
The main driver for this release is that it contains a fix for a serious
vulnerability that was responsibly reported last week by Felix Wilhelm
from Google Project Zero, affecting the HPACK decoder used f
Hi,
HAProxy 2.1.4 was released on 2020/04/02. It added 99 new commits
after version 2.1.3.
The main driver for this release is that it contains a fix for a serious
vulnerability that was responsibly reported last week by Felix Wilhelm
from Google Project Zero, affecting the HPACK decoder used for
Hi here
These patches introduce a few function to the ist API and also a converter
to validate a FIX message and to extract data from a FIX payload.
Thx at Christopher for his help during this dev.
Baptiste
From 4e9de7128c7065dc01b423dcce13b18487f1f353 Mon Sep 17 00:00:00 2001
From: Baptiste Ass
Hello,
ongoing typo fixes.
Ilya Shipitcin
From f0ba77f8d64c301ac8877e3d2850a7966acea658 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 2 Apr 2020 15:25:26 +0500
Subject: [PATCH] CLEANUP: assorted typo fixes in the code and comments
This is sixth iteration of typo fixes
---
contrib/de
forgot to attach a ptach itself ))
чт, 2 апр. 2020 г. в 15:04, Илья Шипицин :
> Hello,
>
> this patch should resolve https://github.com/haproxy/haproxy/issues/553
>
> Cheers,
> Ilya Shipitcin
>
From 36dec6691e98dd92760c1434411aab207e43b93b Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu,
Hello,
this patch should resolve https://github.com/haproxy/haproxy/issues/553
Cheers,
Ilya Shipitcin
Hi.
On 02.04.20 09:36, Matthias Zepf wrote:
Hi,
for a client we develop a web shop application that handles payment by
redirecting the user to a page of a payment service provider. After successful
(or failed) payment the user is redirected back to our application with a post
request. With C
Hi,
for a client we develop a web shop application that handles payment by
redirecting the user to a page of a payment service provider. After successful
(or failed) payment the user is redirected back to our application with a post
request. With Chrome 80 this began to be a problem because on
23 matches
Mail list logo