Daniel Blumenthal wrote:
How does the lb decide where you go for all requests after the first one? Typically, the session id is sniffed from the URL or cookie and the lb maintains a table of mappings that expires after some time.
Our two choices are evidently "IP-based" and "cookie-based". Currently, we're using "IP-based", so every IP address is treated as a separate request. I'm looking into making it cookie-based, and making cookies a requirement for the site (currently, we only use cookies to store a couple of simple preferences). Any idea how many people have cookies turned off?
Are you *sure* your load balancer isn't capable of recognising session IDs in URLs? If it can, then you have a 3rd option: forget cookies and tell Tomcat to use URL encoding exclusively. Of course, you must call response.encodeURL() anywhere you return a link back into the session, but this is probably good practice anyway, and all cookie-related problems go away (and testing becomes easier: you can have many independent sessions in Firefox tabs etc. :-) Paul Singleton --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
