if you use haproxy with app-generated-cookie based balancing, it will continue
to send requests with that cookie to that backend as long as that cookie
exists and that backend is up - afaik.
If you look at the cookie in a browser tool, what is the expiration time?
If it is not, as long as you want you have to change the expiration time in
your CMS that is creating the cookie.
On 9/3/09 8:15 AM, James Little wrote:
Hi All,
I'm looking for some advice on how to achieve lengthly (2 hours+)
persistence with cookie insertion. I know that by default the cookies do
not expire, but we are concerned here with the actual session duration.
For example, say we are dealing with a web-based CMS where the user
wants to be logged in for hours, but is not necessarily refreshing the
screen frequently. How do we ensure he stays logged in? I'm aware that
HAProxy does not support http keep-alive. Is the 'clitimeout' setting
the right way to go?
Also interested in knowing the *default* persistence timeout.
Any pointers greatly appreciated.
James
