Re: regtest failure for /cache/h00000.vtc, config parsing fails? after commit 7805e2b

Le 01/12/2018 à 22:48, PiBa-NL a écrit : Hi Christopher, List A recent commit http://git.haproxy.org/?p=haproxy.git;a=commit;h=7805e2bc1faf04169866c801087fd794535ecbb2 seems to have broken config parsing for some configurations as seen with reg-test: /cache/h0.vtc Using: haproxy version: 1.

Re: regtest failure for /cache/h00000.vtc, config parsing fails? after commit 7805e2b

On Sun, Dec 02, 2018 at 09:58:40AM +0100, Christopher Faulet wrote: > Argh! You're right. I was in hurry to finish all my work on the HTX. Here is > a fix. Applied, thanks Christopher. I initially thought the problem was on my side but I was too busy integrating the rest of the stuff we have to ta

Re: acme proxy for internal use

On Sat, Dec 1, 2018 at 9:18 PM Joel Linn wrote: > > Hi, > > I want to use letsencrypt for services in my intranet. > The acme protocol demands that a challenge response is published under > http://certname.domain.tld/.well-known/acme-challenge/xyz > All subdomains under domain.tld get forwarded fr

Re: [PATCH] REGTEST: Fix LEVEL 4 script 0 of "connection" module.

On Thu, Nov 29, 2018 at 02:28:07PM +0100, Frederic Lecaille wrote: > Here is a little reg test fix. Applied, thanks Fred. Willy

Re: [PATCH] MINOR: dns: Set maximum DNS udp payload at 65507

On Thu, Oct 18, 2018 at 05:52:47PM +0200, Anthonin Bonnefoy wrote: > From: Anthonin Bonnefoy > > With EDNS, DNS packets can have a maximum size of 65507. > This will allow to have a bigger accepted_payload_size which is useful > when we have more than 100 SRV records. Baptiste, please have a loo

Re: [PATCH] CLEANUP: Fix typos in the proto_tcp subsystem

Hi Joseph, On Sun, Nov 25, 2018 at 12:35:21PM -0800, Joseph Herlant wrote: > Will do, thanks! > On Sun, Nov 25, 2018 at 12:10 PM William Lallemand > wrote: > > > > On Sun, Nov 25, 2018 at 11:30:06AM -0800, Joseph Herlant wrote: > > > Sorry, I forgot the attachement on this one. > > > > Hi Joseph,

haproxy config order

Hello, I am from sous-chefs, the Chef Community team that maintains a chef cookbook for haproxy. We have found that haproxy warns or alerts on various configuration ordering and would like to update our cookbook to handle this ordering. A specific example would be the warning: "a 'http-request' r

[ANNOUNCE] haproxy-1.9-dev9 : the last mile

Hi, HAProxy 1.9-dev9 was released on 2018/12/02. It added 147 new commits after version 1.9-dev8. This version will give some of us a bit of relief. It is the first one in one year which finally integrates all the ongoing parallel development! I thought about calling it -rc1 but I remembered that

behavior change when enabling HTX (in regtest /connection/b00000.vtc)

Hi List, When running regtest /connection/b0.vtc with the added setting below: defaults     option http-use-htx The test no longer completes successfully, is this 'by design' ? It seems its not closing the server connection? Or at least not logging so, which i guess is why the log line i

Re: behavior change when enabling HTX (in regtest /connection/b00000.vtc)

Hi Pieter, On Mon, Dec 03, 2018 at 12:30:37AM +0100, PiBa-NL wrote: > Hi List, > > When running regtest /connection/b0.vtc with the added setting below: > > defaults > >     option http-use-htx > > The test no longer completes successfully, is this 'by design' ? It seems > its not closing

Re: haproxy config order

Hello John, On Sun, Dec 02, 2018 at 01:18:51PM -0600, John Roesler wrote: > Hello, > > I am from sous-chefs, the Chef Community team that maintains a chef > cookbook for haproxy. We have found that haproxy warns or alerts on various > configuration ordering and would like to update our cookbook t