Re: try other backend when backlog is full or backend unavailable, but only in that case

Hey, You can use options "retries" and "redispatch". As soon as HAProxy has sent a request to a server, it's not available anymore in its buffer. So you're sure it won't be sent again to an other server. Cheers On Fri, Jun 15, 2012 at 2:06 PM, Gábor Farkas wrote: > hi, > > currently i use nginx

Re: Rate limiting based on X-Forwarded-For

Hey, You could do it through 2 HAProxy instances: - the first instance use the IP address from the X-forward-for header to get connected on the second one (through the proxy protocol, using a patched kernel). - the second can rate limit based on the source IP provided through the proxy protocol.

try other backend when backlog is full or backend unavailable, but only in that case

hi, currently i use nginx to handle a configuration, but i'm unable to do there what i need, so i'm looking into haproxy, if i could use it for load-balancing. what i'd like to achieve is: - i have mutliple backends (let's say 2: backend-a, backend-b) - when a request comes in, i want it to be pr

bind keyword

Hi, In the documentation for 1.4.18 in the keyword matrix it states that the bind configuration keyword is only valid within listen or frontend sections. However I've created a backend section that not only allows the keyword, but also creates a socket (which doesn't seem to respond to any request