Re: [PATCH v2 2/3] MINOR: config: allow no set-dumpable config option

Here are the adjustments I'm proposing (only 2 and 3 were slightly touched). I'm not committing them without your consent since they were signed-off :-) Just let me know. Thanks, Willy >From 7f36164b38965c4c8a8df8d5aadbc31cafd39986 Mon Sep 17 00:00:00 2001 From: William Dauchy Date: Sun, 27 Oct

Re: [PATCH v2 2/3] MINOR: config: allow no set-dumpable config option

Hi William, I'm taking the patchset. However I'll apply some small changes : On Sun, Oct 27, 2019 at 08:08:10PM +0100, William Dauchy wrote: > in global config parsing, we currently expect to have a possible no > keyword (KWN_NO), but we never allow it in config parsing. > another patch could

Re: cygwin builds

On Sun, Oct 27, 2019 at 08:20:48PM +0500, ??? wrote: > BUILD: CI: comment out cygwin build, upgrade various ssl libraries > > cirrus ci builds are now limited to branches master, next > travis-ci images are upgraded to ubuntu bionic > cygwin builds are temporarily

Re: Deprecating a few keywords for 2.1+

On Tue, Oct 29, 2019 at 12:40:52AM +0100, Aleksandar Lazic wrote: > > Or maybe something like: > > http-request deny deny_status 500 if { path_beg /health } { > > nbsrv(yourbackend) lt 1 } > > http-request deny deny_status 200 if { path_beg /health } > > Looks good but 'deny' and '200' feels

Re: Deprecating a few keywords for 2.1+

Am 28.10.2019 um 17:44 schrieb Jarno Huuskonen: On Mon, Oct 28, Aleksandar Lazic wrote: Am 27.10.2019 um 20:16 schrieb David Birdsong: I'm just curious: what replaces monitor-uri? I'm putting up a new proxy tier at my new company and can steer to use the more up-to-date method, but combing the

Re: Deprecating a few keywords for 2.1+

Am 28.10.2019 um 17:43 schrieb David Birdsong: On Mon, Oct 28, 2019 at 12:27 PM Aleksandar Lazic > wrote: Am 27.10.2019 um 20:16 schrieb David Birdsong: > I'm just curious: what replaces monitor-uri? I'm putting up a new proxy tier at > my new

Re: Truncated response on 2.0.8

Le 28/10/2019 à 15:49, Ing. Andrea Vettori a écrit : If it is on a development platform, is there any way to have a full network capture ? Thanks for your help. The server where haproxy is running is a production server while this specific front/backend is a development web site. I can

Re: Mode TCP and acl to choose backend

Hi, On Mon, Oct 28, Philipp Kolmann wrote: > I load-balance TCP Port 25 on a haproxy. This works perfect. > > Now I need to check, if the connection is coming for a special host, then a > different backend smtp server should be used. I thought I could use acl and > use_backend but this seems

Re: Deprecating a few keywords for 2.1+

On Mon, Oct 28, Aleksandar Lazic wrote: > Am 27.10.2019 um 20:16 schrieb David Birdsong: > > I'm just curious: what replaces monitor-uri? I'm putting up a new proxy > > tier at my new company and can steer to use the more up-to-date method, > > but combing the docs and nothing jumps out at me. > >

Re: Deprecating a few keywords for 2.1+

On Mon, Oct 28, 2019 at 12:27 PM Aleksandar Lazic wrote: > Am 27.10.2019 um 20:16 schrieb David Birdsong: > > I'm just curious: what replaces monitor-uri? I'm putting up a new proxy > tier at > > my new company and can steer to use the more up-to-date method, but > combing the > > docs and

Re: Deprecating a few keywords for 2.1+

Am 27.10.2019 um 20:16 schrieb David Birdsong: I'm just curious: what replaces monitor-uri? I'm putting up a new proxy tier at my new company and can steer to use the more up-to-date method, but combing the docs and nothing jumps out at me. I'm guessing something in either

Cooperation with you

Greetings! My name is Lucas, I am ADSmarket.org SEO consultant. I’m interested in your resource dev.haproxy.org as an advertising platform. Could it be interesting for you? If this is the case, then I want to ask you a few questions for further cooperation: 1. Do you accept press releases?

Re: Status of 1.5 ?

Hi. Am 25.10.2019 um 11:27 schrieb Willy Tarreau: Hi all, I'm just wondering what to do with 1.5. I've checked and it didn't receive any fix in almost 3 years. The ones recently merged into 1.6 that were possible candidates for 1.5 were not critical enough to warrant a new release for a long

[PATCH V3] MINOR: sample: add us/ms support to date sample

It can be sometimes interesting to have a timestamp with a resolution of less than a second. It is currently painful to obtain this, because concatenation of date and date_us lead to a shorter timestamp during first 100ms of a second, which is not parseable and needs ugly ACLs in configuration to

Re: Truncated response on 2.0.8

> On 28 Oct 2019, at 11:51, Christopher Faulet wrote: > > Le 26/10/2019 à 18:10, Ing. Andrea Vettori a écrit : >> Hello, >> I'm using haproxy 2.0.8 and ssl termination with h2 and http1.1 protocols. >> Since today we always used http1.1 on the backends. >> I’ve tried to use http2 on the

Mode TCP and acl to choose backend

Hi, I load-balance TCP Port 25 on a haproxy. This works perfect. Now I need to check, if the connection is coming for a special host, then a different backend smtp server should be used. I thought I could use acl and use_backend but this seems only to work for http connections. Has anyone a

[PATCH V2] MINOR: sample: add us/ms support to date sample

It can be sometimes interesting to have a timestamp with a resolution of less than a second. It is currently painful to obtain this, because concatenation of date and date_us lead to a shorter timestamp during first 100ms of a second, which is not parseable and needs ugly ACLs in configuration to

Re: Truncated response on 2.0.8

Le 26/10/2019 à 18:10, Ing. Andrea Vettori a écrit : Hello, I'm using haproxy 2.0.8 and ssl termination with h2 and http1.1 protocols. Since today we always used http1.1 on the backends. I’ve tried to use http2 on the development backend but I get truncated response (not always but very

Re: Truncated response on 2.0.8

On 2019-10-26 18:10, Ing. Andrea Vettori wrote: Hello, I'm using haproxy 2.0.8 and ssl termination with h2 and http1.1 protocols. Since today we always used http1.1 on the backends. I’ve tried to use http2 on the development backend but I get truncated response (not always but very often).