A better way to set this up might be to use a reverse proxy in front of
www1.test.com and www2.test.com. Users would go to www.test.com and the
reverse proxy would forward communications between the front-end and the
servers in the back, thereby balancing the load. Cookies should still work
Or save it to a common database... and it could have something to do with
session.cooke_domain.
A cooke set explicity to www1.test.com won't be viewable on www2.test.com,
but if you set the domain to .test.com it will...
On Thu, 25 Apr 2002, Dan Harrington wrote:
Couldn't you store the
2 matches
Mail list logo
