[imp] cookie domain

[Ramon Kagan]

Alternatively you could use a load balancer like lvs with a
persistance/sticky mechanism that will take care of that.  This will ship
a user to one of the backend machines for the duration of their
connections.  We use this for 3 machines currently and soon 5 for our
currently 40,000 and soon to be 55,000 users.  If you're using linux, try
http://www.linuxvirtualserver.org/ it's an effective tool.  In terms of
resources it's just about transparent (a bit of memory 64-128 K)  We
currently have our persistance set to 4 hours, but it's best to match the
value to the php session garbage collection max time.

Ramon Kagan
York University, Computing and Network Services
Unix Team -  Intermediate System Administrator
(416)736-2100 #20263
rkagan@yorku.ca

On Sun, 17 Mar 2002, Chuck Hagenbuch wrote:

> Quoting Jie Gao <J.Gao@isu.usyd.edu.au>:
>
> > The idea is to use mod_rewrite in Apache to make a reverse proxy, and
> > pass requests to two or more backend servers. The question is if the
> > cookie mechanism will work? If the cookies are sent back to servers
> > that issued them, this won't work. If there is a setting that we can
> > change to make the cookies sent back to a domain, this might just
> > work, I think.
>
> Setting the cookie domain to .domain.com should do the trick.
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck@horde.org>
> "A dream which helps you to live your reality with dignity
>  and justice is a good dream." - Tariq Ramadan
>
> --
> IMP mailing list: http://horde.org/imp/
> Archive: http://marc.theaimsgroup.com/?l=imp&r=1&w=2
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe@lists.horde.org
>