Well in case of header you would have something like this I guess: tcp-request content track-sc1 hdr(x-app-authorization)
On Thu, Oct 1, 2015 at 9:47 AM, Jason J. W. Williams < [email protected]> wrote: > Wondered about that... Do the "tcp-request" rate limiters use the stick > table (I assume they need type ip) or another implied table? > > -J > > On Wed, Sep 30, 2015 at 3:41 PM, Igor Cicimov < > [email protected]> wrote: > >> The stick-table type would be string and not ip in that case though >> >> On 01/10/2015 5:07 AM, "Jason J. W. Williams" <[email protected]> >> wrote: >> > >> > We've been seeing CenturyLink and a few other residential providers >> NATing their IPv4 traffic, making client persistency on source IP result in >> really lopsided load balancing lately. >> > >> > We'd like to convert to sticking on a custom header we're already using >> that IDs the user. There isn't a lot of examples of this, so I was curious >> if this is the right approach: >> > >> > Previous "stick on src" config: >> https://gist.github.com/williamsjj/7c3876d32cab627ffe70 >> > >> > New "stick on header" config: >> https://gist.github.com/williamsjj/f0ddc58b9d028b3fb906 >> > >> > Thank you in advance for any advice. >> > >> > -J >> >> The stick-table type would be string and not ip in that case though >> > > -- Igor Cicimov | DevOps p. +61 (0) 433 078 728 e. [email protected] <http://encompasscorporation.com/> w*.* encompasscorporation.com a. Level 4, 65 York Street, Sydney 2000
