Well, I considered the collision domain very very tight ;)
Now, it's easy to prefix the cookie with some values to avoid collisions.
cheers
On Mon, Mar 19, 2012 at 9:54 PM, Willy Tarreau <w...@1wt.eu> wrote:
> On Mon, Mar 19, 2012 at 09:48:31PM +0100, Baptiste wrote:
>> Hey,
>>
>> Here is a configuration sample which may work with latest HAProxy version:
>>
>> stick-table type string len 32 size 10K
>> stick store-response set-cookie(sessionID)
>> stick store-response set-cookie(routeID)
>>
>> sitck on cookie(sessionID) if { hdr_sub(Cookie) sessionID }
>> stick on cookie(routeID) if { hdr_sub(Cookie) routeID }
>>
>> stick on url_param(sessionID) if { url_sub sessionID }
>> stick on url_param(routeID) if { url_sub routeID }
>>
>> I've not tested it, but it should work.
>> Of course, you can combined several ACLs to be more accurate.
>
> You should not store two different cookies into the same table, really.
> Otherwise some conflicting values will cause behaviours which will be
> very hard to troubleshoot.
>
> In theory, only one of them is needed, better use the routeID as
> nginx is supposed to do the rest of the work then.
>
> Willy
>
