Hi Baptise, Thanks for the suggestion. The list of possible values is in 100s and I would like to load balance on different machines while still keeping them sticky. So, stick tables is the ideal solution. However, stick tables only support pattern extractions which are limited to using full values of a header or using url parameters.
Using the acls would mean a) writing 100s of acls and adding more acls whenever a new possible value is added. b) defining a server statically for every possible value instead of letting haproxy choose a server based on load balancing algorithm. Is there a plan to add stick table pattern extraction which includes extraction values from path or header using regular expressions? Thanks, Vivek On Fri, Mar 1, 2013 at 12:54 AM, Baptiste <bed...@gmail.com> wrote: > On Thu, Feb 28, 2013 at 7:28 PM, Vivek Malik <vivek.ma...@gmail.com> > wrote: > > Hi, > > > > I see that it is possible to haproxy sticky on a header value, path, > query > > parameter. It seems that haproxy does process the request URI to extract > > query parameters. Is is possible to use stick tables with stickyness on a > > value extracted from header? > > > > Eg: HTTP request includes header > > > > X-Custom-Authorization: 2-y89nfsjdhns > > > > Is is possible to make haproxy extract 2 i.e. (^(\d+)-.+) from the custom > > header and stick on the extracted value. > > > > Thanks, > > Vivek > > Hi Vivek, > > Better using the below acl: > hdr_beg(X-Custom-Authorization) 2 > > you can add as many values as you want. > > Baptiste >
