Re: haproxy issue tracker discussion

Hi Lukas, On Sat, Jan 12, 2019 at 02:53:45AM +0100, Lukas Tribus wrote: > Hi Tim, Willy, > > apologies for not responding sooner, I always have to force myself to > policy/organizational discussions, when I can also read stack or > straces :) You really don't need to apologize :-) > > So in the

Re: haproxy issue tracker discussion

Hi Tim, Willy, apologies for not responding sooner, I always have to force myself to policy/organizational discussions, when I can also read stack or straces :) >> When should the binary "issue open" / "issue closed" property be >> toggled? When the issue is fixed in Dev? When the issue is fix

Re: Lots of mail from email alert on 1.9.x

Hi Olivier, Op 11-1-2019 om 19:17 schreef Olivier Houchard: Ok so erm, I'd be lying if I claimed I enjoy working on the check code, or that I understand it fully. However, after talking with Willy and Christopher, I think I may have comed with an acceptable solution, and the attached patch shoul

Re: Lots of mail from email alert on 1.9.x

On Fri, Jan 11, 2019 at 06:53:11PM +0100, Olivier Houchard wrote: > Hi, > > On Fri, Jan 11, 2019 at 10:36:04AM +0100, Johan Hendriks wrote: > > Thanks all. > > No rush on my side as it is a test machine, at least we do know when a > > backend server fails. > > With all this mail the mail server ar

Re: Lots of mail from email alert on 1.9.x

Hi, On Fri, Jan 11, 2019 at 10:36:04AM +0100, Johan Hendriks wrote: > Thanks all. > No rush on my side as it is a test machine, at least we do know when a > backend server fails. > With all this mail the mail server are giving alarms too :D > > I disable the mail feature for now. > > Thanks agai

[PATCH 01/10] MINOR: cfgparse: Extract some code to be re-used.

From: Frédéric Lécaille Create init_peers_frontend() function to allocate and initialize the frontend of "peers" sections (->peers_fe) so that to reuse it later. May be backported to 1.5 and newer. --- src/cfgparse.c | 34 ++ 1 file changed, 26 insertions(+), 8 d

[PATCH 06/10] MINOR: cfgparse: Simplication.

From: Frédéric Lécaille Make init_peers_frontend() be callable without having to check if there is something to do or not. May be backported to 1.5 and newer. --- src/cfgparse.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/cfgparse.c b/src/cfgparse.c index 22a3

[PATCH 05/10] MINOR: cfgparse: Rework peers frontend init.

From: Frédéric Lécaille Even if not already the case, we suppose that the frontend "peers" section may have been already initialized outside of "peer" line, we seperate their initializations from their binding initializations. May be backported to 1.5 and newer. --- src/cfgparse.c | 50

[PATCH 10/10] DOC: peers: SSL/TLS documentation for "peers"

From: Frédéric Lécaille --- doc/configuration.txt | 23 ++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 888515fb..d55e4bd3 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -1928,6 +1928,12

[PATCH 04/10] MINOR: cfgparse: Useless frontend initialization in "peers" sections.

From: Frédéric Lécaille Use ->local "peers" struct member to flag a "peers" section frontend has being initialized. This is to be able to initialize the frontend of "peers" sections on lines different from "peer" lines. May be backported to 1.5 and newer. --- src/cfgparse.c | 17 +--

[PATCH 07/10] MINOR: cfgparse: Make "peer" lines be parsed as "server" lines.

From: Frédéric Lécaille With this patch "default-server" lines are supported in "peers" sections to setup the default settings of peers which are from now setup when parsing both "peer" and "server" lines. May be backported to 1.5 and newer. --- src/cfgparse.c | 88 +++--

[PATCH 03/10] CLEANUP: cfgparse: Code reindentation.

From: Frédéric Lécaille May help the series of patches to be reviewed. May be backported to 1.5 and newer. --- src/cfgparse.c | 72 +- 1 file changed, 36 insertions(+), 36 deletions(-) diff --git a/src/cfgparse.c b/src/cfgparse.c index 66

[PATCH 08/10] MINOR: peers: Make outgoing connection to SSL/TLS peers work.

From: Frédéric Lécaille This patch adds pointer to a struct server to peer structure which is initialized after having parsed a remote "peer" line. After having parsed all peers section we run ->prepare_srv to initialize all SSL/TLS stuff of remote perr (or server). Remaining thing to do to com

[PATCH 02/10] CLEANUP: cfgparse: Return asap from cfg_parse_peers().

From: Frédéric Lécaille Avoid useless code indentation. May be backported to 1.5 and newer. --- src/cfgparse.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/cfgparse.c b/src/cfgparse.c index 6fde7c9f..6670a861 100644 --- a/src/cfgparse.c +++ b/src/cfgparse.c @@ -

[PATCH 00/10] Peers SSL/TLS support

From: Frédéric Lécaille Hi ML, With this series of patches we add the SSL/TLS support to haproxy peers. Regards, Fred. Frédéric Lécaille (10): MINOR: cfgparse: Extract some code to be re-used. CLEANUP: cfgparse: Return asap from cfg_parse_peers(). CLEANUP: cfgparse: Code reindentation.

[PATCH 09/10] MINOR: cfgparse: SSL/TLS binding in "peers" sections.

From: Frédéric Lécaille This patch makes "bind" work in "peers" sections. All "bind" settings are supported, excepted ip:port parameters which are provided on "peer" (or server) line matching the local peer. After having parsed the configuration files ->prepare_bind_conf is run to initialize all

Keep client side open on FIN till backend responds

Hi, everybody! I'm facing an issue with a somewhat weird/broken client and I'm looking for some advise on it. The client opens a HTTPS session and sends its request (POST data in my case). The HTTPS part is fine. The POST data is small, so it fits into a single TCP packet, which arrives with ACK,

Re: Lots of mail from email alert on 1.9.x

Thanks all. No rush on my side as it is a test machine, at least we do know when a backend server fails. With all this mail the mail server are giving alarms too :D I disable the mail feature for now. Thanks again Pieter, Willy and Oliver for all your work. Op 10-01-19 om 20:05 schreef PiBa-NL:

[PATCH 2/2] REGTEST: Adapt reg test doc files to vtest.

From: Frédéric Lécaille This is a first patch to switch from varnishtest to new standalone varnish cache reg testing program: vtest. More information may be found here: https://github.com/vtest/VTest https://varnish-cache.org/docs/trunk/reference/varnishtest.html https://varnish-cache.org/docs/

[PATCH 0/2] Switch to vtest.

From: Frédéric Lécaille Hi ML, With these patches, haproxy switches to the new varnish cache reg testing tool named vtest, formerly known as varnishtest. From the user point of view, there is no very much differences compared to the usage of varnishtest. Before we started the reg testing proces

[PATCH 1/2] REGTEST: Switch to vtest.

From: Frédéric Lécaille This patch replace the usage of the formerly varnish cache reg testing program, name varnishtest by the new standalone one: vtest. --- Makefile| 10 +- scripts/run-regtests.sh | 28 ++-- 2 files changed, 19 insertions(+), 19

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

On 1/11/19 12:35 AM, Cyril Bonté wrote: Hi all, Le 08/01/2019 à 10:06, Willy Tarreau a écrit : On Tue, Jan 08, 2019 at 09:31:22AM +0100, Frederic Lecaille wrote: Indeed this script could worked with a short mailer timeout before af4021e6 commit. Another git bisect shows that 53216e7d introduce