RE: Either ACL result is inconsistent or http-server-close isn't working

Hi Gustavo, > Below is my haproxy.cfg:  We will need to know the exact release you are using, because they have different defaults. Regards, Lukas

La façon la plus rapide et la plus facile de nettoyer les pare-brises

Re: use part of url - as backend name?

I got this to work: use_backend %[path,lower,map_reg(/path/tofile)] and with a map file containing: ^\/sebseb/ ^\/test2/ and so on.. Only issue is the performance hit.. its going to do regex match with path on each line in the map file.. :( I'd prefer to find a function to replace path..

Re: Either ACL result is inconsistent or http-server-close isn't working

Right, sorry. I compiled 1.6.3 from source with the options: TARGET=custom USE_PCRE=1 USE_LINUX_SPLICE=1 USE_LINUX_TPROXY=1 USE_OPENSSL=yes Gustavo On 28 January 2016 at 16:47, Lukas Tribus wrote: > Hi Gustavo, > > > > Below is my haproxy.cfg: > > We will need to know the

Re: Either ACL result is inconsistent or http-server-close isn't working

Hi Lukas, I have changed my configurations accordingly and it's working. Thank you very much! Gustavo On 28 January 2016 at 18:04, Lukas Tribus wrote: > Hi Gustavo, > > > > > I compiled 1.6.3 from source with the options: TARGET=custom USE_PCRE=1 > > USE_LINUX_SPLICE=1

RE: Either ACL result is inconsistent or http-server-close isn't working

Hi Gustavo, > I compiled 1.6.3 from source with the options: TARGET=custom USE_PCRE=1 > USE_LINUX_SPLICE=1 USE_LINUX_TPROXY=1 USE_OPENSSL=yes Unless you have a kernel older than 2.6.28, just use the linux2628 target: TARGET=linux2628 USE_PCRE=1 USE_OPENSSL=1 This will enable all current

haproxy reloads, stale listeners, SIGKILL required

I've been running into a problem for a few weeks that I was hoping to see disappear w/ a simple upgrade to 1.6.3. I'm using consul and it's templating to dynamically expand a backend list which then runs an haproxy reload using the init scripts in the contrib dir. I haven't been able to trace

Re: haproxy reloads, stale listeners, SIGKILL required

On 28/01/2016 10:35 μμ, David Birdsong wrote: > I've been running into a problem for a few weeks that I was hoping to > see disappear w/ a simple upgrade to 1.6.3. > > I'm using consul and it's templating to dynamically expand a backend > list which then runs an haproxy reload using the init

RE: Force client IP with PROXY protocol

>> If you can't use layer 7 features then you can't access the >> CF-Connecting-IP header in nginx. > > ...HAProxy, not Nginx, no ? Yes, I mixed that up, haproxy was what I meant. > Otherwise that would be nice to be able pass client IP address as an > argument to send-proxy directive. >

Re: Force client IP with PROXY protocol

2016-01-28 11:47 GMT+01:00 Lukas Tribus : > Doesn't: > http-request set-src hdr(CF-Connecting-IP) > > in combination with a standard proxy-protocol config > already do that? Yes, but it doesn't work with SPDY or HTTP/2 backends. -- Jonathan Leroy http://www.inikup.com/ Tel:

Re: Force client IP with PROXY protocol

Am 28-01-2016 12:01, schrieb Jonathan Leroy - Inikup: 2016-01-28 11:47 GMT+01:00 Lukas Tribus : Doesn't: http-request set-src hdr(CF-Connecting-IP) in combination with a standard proxy-protocol config already do that? Yes, but it doesn't work with SPDY or HTTP/2

Re: Force client IP with PROXY protocol

2016-01-28 10:56 GMT+01:00 Aleksandar Lazic : > Maybe it would be a nice idea to add something like. > > proxy-protocol set-src hdr(CF-Connecting-IP) > > Opinions about this? Something like "proxy-protocol set-src []", yep :) -- Jonathan Leroy http://www.inikup.com/ Tel:

RE: Force client IP with PROXY protocol

> Maybe it would be a nice idea to add something like. > > proxy-protocol set-src hdr(CF-Connecting-IP) > > Opinions about this? Doesn't: http-request set-src hdr(CF-Connecting-IP) in combination with a standard proxy-protocol config already do that? Lukas

SMTP and STARTTLS support

hi, i'm using HAProxy mainly to redistribute HTTP(S) requests to different backends depending on their domain (via host header) to implement vhosts on a single IP. i'd like to have the same for SMTP, but unfortunately it's much harder, since we get to know the target domain late in the

Re: use part of url - as backend name?

Hi guys, I figured I could use map feature of 1.5, but I'm coming up short, trying to change this: use_backend %[req.hdr(host),lower,map(/path/tofile)] To instead take a part of the uri. I can't find any list of functions (such as hdr, hdr_end etc.) in the docs :( I figured I could use

Re: use part of url - as backend name?

On Fri, Jan 29, 2016 at 2:27 AM, Klavs Klavsen wrote: > I got this to work: > > use_backend %[path,lower,map_reg(/path/tofile)] > > and with a map file containing: > ^\/sebseb/ > ^\/test2/ > > and so on.. > > Only issue is the performance hit.. its going to do regex match with path

Re: haproxy reloads, stale listeners, SIGKILL required

On Thu, Jan 28, 2016 at 6:35 PM, Pavlos Parissis wrote: > On 28/01/2016 10:35 μμ, David Birdsong wrote: > > I've been running into a problem for a few weeks that I was hoping to > > see disappear w/ a simple upgrade to 1.6.3. > > > > I'm using consul and it's

Re: use part of url - as backend name?

Hi, I am not sure if there is a better way, but the only one I can think of would be something like: http-request set-header X-Tmp %[path] http-request replace-header X-Tmp /([^/]+) \1 use_backend %[req.hdr(X-Tmp),lower,map(/path/tofile)] No idea which one is preferable with regards