Re: Re: haproxy does not capture the complete request header host sometimes

On Wed, May 31, 2017 at 10:15:56AM +0800, siclesang wrote: > i am sorry > -d output > 954722 000513c:.accept(0008)=000a from [10.201.10.11:10037] > 954723 000513c:.clihdr[000a:] POST /coupon/show/a511 HTTP/1.1 > 954724 000513c:.clihdr[000a:] Connection: keep-alive >

Re:Re: haproxy does not capture the complete request header host sometimes

i am sorry -d output 954722 000513c:.accept(0008)=000a from [10.201.10.11:10037] 954723 000513c:.clihdr[000a:] POST /coupon/show/a511 HTTP/1.1 954724 000513c:.clihdr[000a:] Connection: keep-alive 954725 000513c:.clihdr[000a:] ent-Type:

Re:Re: haproxy does not capture the complete request header host sometimes

i am sorry -d output 954722 000513c:.accept(0008)=000a from [10.201.10.11:10037] 954723 000513c:.clihdr[000a:] POST /coupon/show/a511 HTTP/1.1 954724 000513c:.clihdr[000a:] Connection: keep-alive 954725 000513c:.clihdr[000a:] ent-Type:

BUG: Seg fault when reloading from saved state after config change

BUG: Extra spaces inserted into the haproxy.cfg file cause haproxy reload with saved state to seg fault haproxy. WORKAROUND: Remove the existing state file OR remove save state from config. REPRODUCE: - Enable save state across reloads - Reload and save state file - Insert extra space

Re: HAProxy 1.7.5 cookie JSESSIONID prefix not working

Hello Norman, Am 31.05.2017 um 00:13 schrieb Norman Branitsky: > > You are correct. > > I was setting the jvmRoute parameter to be the server id (AWS EC2 > InstanceID) in my regular apps served by HAPRoxy 1.5.18. > > The HAProxy 1.7.5 testing is using a different app that obviously > doesn't

RE: HAProxy 1.7.5 cookie JSESSIONID prefix not working

You are correct. I was setting the jvmRoute parameter to be the server id (AWS EC2 InstanceID) in my regular apps served by HAPRoxy 1.5.18. The HAProxy 1.7.5 testing is using a different app that obviously doesn't have the jvmRoute defined. Should I continue with adding "cookie id" to the

Re: HAProxy 1.7.5 cookie JSESSIONID prefix not working

Hi Norman, Le 30/05/2017 à 23:39, Norman Branitsky a écrit : I modified the server line thus: server id-dv-dcavr-01 10.90.10.53:9001 check cookie id-dv-dcavr-01 Now the server name appears as a prefix with a "~" separator. (It used to appear as a suffix with a "." separator.) No,

RE: HAProxy 1.7.5 cookie JSESSIONID prefix not working

I modified the server line thus: server id-dv-dcavr-01 10.90.10.53:9001 check cookie id-dv-dcavr-01 Now the server name appears as a prefix with a "~" separator. (It used to appear as a suffix with a "." separator.) JSESSIONID=id-dv-dcavr-01~E8C5E4A2; path=/le5;

Re: HAProxy 1.7.5 cookie JSESSIONID prefix not working

Hi Norman Branitsky. Norman Branitsky have written on Tue, 30 May 2017 16:06:18 +: > With HAProxy 1.5.18, on a RHEL 7.1 server, > > appsession JSESSIONID len 52 timeout 3h > > results in a cookie that looks like this: > >

Re: HAProxy 1.7.5 cookie JSESSIONID prefix not working

Hello Norman, Am 30.05.2017 um 18:06 schrieb Norman Branitsky: > > The server’s identifier is not added to the cookie. > Did you specify the cookie value on the server line [1], as per [2]: > The value of the cookie will be the value > indicated after the >

HAProxy 1.7.5 cookie JSESSIONID prefix not working

With HAProxy 1.5.18, on a RHEL 7.1 server, appsession JSESSIONID len 52 timeout 3h results in a cookie that looks like this: JSESSIONID=51CC2775.i-07035eca525e56235; path=/le5; domain=vr.ras.dshs.state.tx.us; Secure; HttpOnly With HAProxy 1.7.5, on a CentOS 7 server, since

Re: HAProxy won't shut down

On 2017/5/29 16:04, Frederic Lecaille wrote: > On 05/29/2017 06:12 PM, Patrick Hemmer wrote: >> >> On 2017/5/29 08:22, Frederic Lecaille wrote: >>> >>> Hi Patrick, >>> >>> First thank you for this nice and helpful report. >>> >>> Would it be possible to have an output of this command the next

Re: [PATCH 6/9] MEDIUM: mworker: workers exit when the master leaves

On Tue, May 30, 2017 at 12:39:32PM +0200, Willy Tarreau wrote: > [...] > > The master, not intercepting this signal, would die, closing the pipe. > The worker would be woken up on the detection of this closure, and while > trying to perform the read() would get the signal in turn, causing the >

Re: New feature request

On 05/30/2017 11:56 AM, Willy Tarreau wrote: > On Tue, May 30, 2017 at 11:04:35AM +0200, Pavlos Parissis wrote: >> On 05/29/2017 02:58 PM, John Dison wrote: >>> Hello, >>> >>> in ROADMAP I see: >>> - spare servers : servers which are used in LB only when a minimum farm >>> weight threshold is not

Re: [PATCH 6/9] MEDIUM: mworker: workers exit when the master leaves

So all the series looks quite good, and I must confess I'm impatient to merge it so that we turn the page of the wrapper, and also because being able to use nbproc in foreground during development can be nice. But I have two comments first : On Mon, May 29, 2017 at 05:42:09PM +0200, William

Re: New feature request

On Tue, May 30, 2017 at 11:04:35AM +0200, Pavlos Parissis wrote: > On 05/29/2017 02:58 PM, John Dison wrote: > > Hello, > > > > in ROADMAP I see: > > - spare servers : servers which are used in LB only when a minimum farm > > weight threshold is not satisfied anymore. Useful for inter-site LB

Re: New feature request

On 05/29/2017 02:58 PM, John Dison wrote: > Hello, > > in ROADMAP I see: > - spare servers : servers which are used in LB only when a minimum farm > weight threshold is not satisfied anymore. Useful for inter-site LB with > local pref by default. > > > Is it possible to push this item priority