Re: [PATCH] MINOR: send-proxy-v2: sends authority TLV according to TLV received

> Le 31 août 2019 à 12:29, Willy Tarreau a écrit : > > Hi Manu, > > On Thu, Aug 29, 2019 at 03:22:11PM +0200, Emmanuel Hocdet wrote: >> This patch follows Geoff's patch. > > Thanks for this. I didn't remember we automatically copied the SNI > into the PP. I'm suspecting that sooner or later

Re: HAProxy 2.0 "stick on src table mypeers/mytable" does not result in peers binding to socket address

Hi Fred, On Mon, Sep 02, 2019 at 02:23:19PM +0200, Frederic Lecaille wrote: > On 8/31/19 12:20 PM, Willy Tarreau wrote: > > Hi Bruno, > > > > On Sat, Aug 31, 2019 at 12:49:15AM +, Bruno Henc wrote: > > > Greetings, > > > > > > Using "stick on src table mypeers/stickysrc" in a backend

Re: HAProxy 2.0 "stick on src table mypeers/mytable" does not result in peers binding to socket address

On 8/31/19 12:20 PM, Willy Tarreau wrote: Hi Bruno, On Sat, Aug 31, 2019 at 12:49:15AM +, Bruno Henc wrote: Greetings, Using "stick on src table mypeers/stickysrc" in a backend results in HAProxy deciding not to bind to the appropriate peers address for the local host (i.e. HAProxy thinks

Setting SSL/TLS options but still allow some exceptions

Hello, I'm rewriting a complex HAProxy config file and would like to be sure how ssl-default-bind-options and bind options work together. I would like to configure safe options by default, but still allow less-safe protocols on some frontend. I'm puzzled by "force-X" documentation (does it really

BUG/MEDIUM: spoe: engine-id is necessary if not health check

Hi Christopher SPOE engine-id is all same when nbproc is more than 1, the clients all group under same engine, and same stream-id and frame-id frames may come at same time. So we alway need engine-id to identify client's and frames. Best Regards From caedabe336897704b4da39818ac7d226c7b8a9db Mon