hi tony!
if possible, simply write a wrapper (register a custom session handler..) for
php to use
a database for storing/getting the session data. this all webservers have
access to the
same data and you dont have to care about session handling at all.
corin
Wednesday, April 12, 2006, 12:56:29 PM, you wrote:
TH> Hi list,
TH> I think the session persistance problem I was having (initially with
2.0.1)
TH> has been tracked down, and it's not a Pound issue. Discovered most of
the
TH> users who were unable to log on to this PHP site were on AOL.
TH> Their proxies will send requests from different IPs for the same
cllient.
TH> This is legal, but obviously breaks IP based session balancing - check
out
TH> cisco advice for the same issue... (search for AOL in the page).
TH> http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_qanda_item09186a00801aa6d1.shtml
TH> So, I now need to balance by some other means. PHP's session code uses a
TH> combination of PHPSESSID as a cookie or as a URL parameter. Has anyone
TH> implemented changes for pound to recognise both these methods
TH> interchangeably, and can we see such a thing in the next revision? Or
has
TH> someone come up with a cunning alternative? :) I can't switch to just
TH> accepting cookies for session IDs as it will lock out some users on
TH> primitive(/secure) browsers.
TH> I can look at implementing said changes, but thought it best to ask
first :)
TH> Thanks,
TH> --
TH> Tony
|
