-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kim,
Kim Albee wrote:
> We are not doing URL rewriting with sessionid, it's saving as a
> cookie.
Okay.
> Not sure how the sessionid is determined ... by Tomcat or Apache
Tomcat generates the sessions and therefore their ids as well.
> we have mul
Chris,
Thanks for the thinking -- I'm aware of the client IP issues with AOL, and
we checked that, but it appears that the IP is staying consistent for our
testing -- but our sessionid still gets changed... We are not doing URL
rewriting with sessionid, it's saving as a cookie... and we can see t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kim,
Kim Albee wrote:
> Client Config:
> AOL Version 9 web browser.
How are you managing sessions? Is the container doing it for you, or are
you doing them yourself? Cookies or URL rewriting? Is the server and/or
session configuration sensitive to th
Server Configuration:
Linux Fedora Core 3, Apache 2.0, Tomcat 5.0.30 session sharing and load
balanced (with session persistence on a server) across two servers (not
using tomcat / JK load balancing).
Client Config:
AOL Version 9 web browser.
When users come in to the site and login, then move
