Re: Cookie/acl priority?

From: Willy Tarreau <w#1wt.eu>
Date: Tue, 27 Nov 2007 22:37:12 +0100


On Tue, Nov 27, 2007 at 02:16:43PM -0700, Dan Zubey wrote:
>
> I have a bit of a problem and a question I need help with.
>
> We have a twisted app server that wants to hand people off to another server to do reporting when they request it.
>
> We're doing cookie-based stickiness as well as session tracking.The handoff to the java server is done by acl.
>
> When the handoff occurs, the entire session seems to go off into the virtual bit-bucket.
>
> How can I get this to work, and have a client jump between servers and allow haproxy to give precedence to the acl (vhost name) while keeping the cookies sticky?

It already works the way you expect it to. The ACL in the frontend selects the backend, and only then the cookie is evaluated in the backend to select a server within this backend.

It is possible that you have used the same cookie name in both backends, which will result in each backend changing the cookie used by the other one. I've already encountered this case between on an HTTP + HTTPS application where there was a different number of servers between both. The client would always use the same cookie between both instances, resulting in some servers being almost never used.

Regards,
Willy Received on 2007/11/27 22:37

This archive was generated by hypermail 2.2.0 : 2007/11/27 23:15 CET