rate-limiting - per src per path

Hi, Is it possible to rate-limit requests per-path-per-src. Sticky-table can be type IP or type String. tcp-request can be either connection or content. I am not an expert and hence the doubt. There are examples on the web but not explained if both src and path can be checked for rate-limiting.

Re: using environment variable in headers

On 06/01/2015 08:42 μμ, Cyril Bonté wrote: Hi Pavlos, Le 06/01/2015 20:17, Pavlos Parissis a écrit : Hi, According to the docs I can have the following snippet http-request add-header Nodename %[env(HOSTNAME)] to set the hostname as the value on a header. But, it doesn't work. I

Send client to a specific backend if header found in previous reply from server

Hello, This is a followup to my post and Baptiste's answer on 20141120. Unfortunately, I couldn't get this to work. I am trying to achieve the following : when a response from the application server contains a header named X-test, send the following requests from the client IP to another

rspitarpit ?

We're getting some congestion from blind-shooting (or maybe just stupid-shooting) scrapers who make (mostly bad) requests, with occasional successes. We'd like to tarpit unsuccessful responses. Any experience on how to accomplish that ? ( A rspitarpit directive would be awesome ) Kudos on an

Stick table and http headers

Hi, Does this seem right? acl HAS_CF_CONNECTING_IP hdr_cnt(CF-Connecting-IP) eq 1 acl HAS_X_FORWARDED_FOR hdr_cnt(x-forwarded-for) eq 1 tcp-request content track-sc0 hdr_ip(CF-Connecting-IP,-1) if HTTP HAS_CF_CONNECTING_IP tcp-request content track-sc0 hdr_ip(x-forwarded-for,-1) if HTTP

errorloc[303] with variables

Hi, Looking at the source it seems implied there may be a way to set the errorloc or errorloc303 destination string to include variables known to HAProxy, rather than a static string. In much the same way that one could set an HTTP request header using certain variables like so: