Setting weight through stats socket, nbproc > 1

I am running haproxy with nbproc 3. (I know its not supported, but i want to use more than 1 cpu with haproxy) The following is my config related to the stats socket daemon nbproc 3 pidfile /var/run/hapxy.pid # Does not work with nbproc >1 stats socket /var/run/h

Re: problems with req.ssl_ec_ext

On Mon, May 30, 2016 at 5:24 PM, Nenad Merdanovic wrote: > Yes, it seems like the case is that the fetch is only called once, when > there is not enough data in the buffer. You can work around this like: > tcp-request inspect-delay 5s > tcp-request content accept if {req.ssl_ec_ext 0 } Thanks a l

Re: problems with req.ssl_ec_ext

On 30/05/2016 05:24 μμ, Nenad Merdanovic wrote: > Hello Bjorn, > > On 5/30/2016 4:29 PM, Björn Zettergren wrote: >> Hi, >> >> I've been playing around with the ECC+RSA certificate on same IP as >> described in the haproxy blog at >> http://blog.haproxy.com/2015/07/15/serving-ecc-and-rsa-certifica

Re: Setting weight through stats socket, nbproc > 1

Hi, On 05/31/2016 11:55 AM, Unknown User wrote: > I am running haproxy with nbproc 3. (I know its not supported, but i > want to use more than 1 cpu with haproxy) Don't worry, it still works really well :) > The following is my config related to the stats socket > > daemon > nbproc 3 >

Re: Melting under high connection rates

Thank you for your detailed response Willy, Some points I should clarify: > On May 30, 2016, at 1:01 PM, Willy Tarreau wrote: > > Hello, > > On Sun, May 29, 2016 at 12:53:21AM +0430, Behrad Zari wrote: >> We have over 90K concurrent TCP persistent connections on our single haproxy >> instanc

Printing products:labels,silk screen nameplate, 3M plastic molding,die-cutting Product and etc.,/vsiuk7与您共享了相册。

Dear Sirs, After visiting your web-site I decided to contact your esteemed company .We are a modern printing enterprise, devoting to design, development, production and services . Our products are accorded with international standards,ISO9001,UL authentication. Relying on strong mana

multi process limitations

Hello everyone, could you please tell me if the limitations with multi-process are still true with HAProxy 1.6 : - frontend(s) and associated backend(s) must run on the same process - not compatible with peers section (stick table synchronisation) ( from here : http://blog.haproxy.com/2015/

'set-dst' and 'set-dst-port' tcp/http actions

Hello, Here a set of patches implementing http/tcp set-{dst,src}[-port]. The feature can be useful to connect to a IP/port which is defined in a map. Regards, -- William Lallemand >From 4f44c85bd02830d690539b269a4669b6bd251e44 Mon Sep 17 00:00:00 2001 From: William Lallemand Date: Wed, 25 May

Re: 'set-dst' and 'set-dst-port' tcp/http actions

I'll give them a try. Are they to be applied to the latest 1.7-dev branch? On Tue, May 31, 2016 at 3:01 PM, William Lallemand wrote: > Hello, > > Here a set of patches implementing http/tcp set-{dst,src}[-port]. > > The feature can be useful to connect to a IP/port which is defined in a > map.

Re: [PATCH] [RFC]/MINOR: connection: Add server name to proxy protocol v2 header.

On 30/05/2016 11:03 p.m., Erik Seres wrote: > Hi Willy and Amos, > > I think I am confused by what information is expected to go into the > PP2_TYPE_AUTHORITY field and how it would be a suitable substitute > for what SNI represents. PP2 is generic and needs to relay multiple protocols. Author

Re: 'set-dst' and 'set-dst-port' tcp/http actions

On Tue, May 31, 2016 at 05:28:13PM -0700, Derek Brown wrote: > I'll give them a try. Are they to be applied to the latest 1.7-dev branch? > That's right. -- William Lallemand