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 the cookie too on the user machine we tested with.
Not sure how the sessionid is determined ... by Tomcat or Apache -- we have multiple servers and session sharing occurring with Tomcat, so we are appending the server ID (worker.id) to the sessionid variable, which Tomcat manaages, but I'm not sure how Apache and/or Tomcat determine the sessionid... do you know how that happens? thanks, Kim :-) On 1/10/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----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 the remote (client) IP address? I notice you are using AOL, which plays games with the remote (client) IP address, so if you are requiring the IP address of the user to stay the same, it's not going to work for AOL users. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFpWtn9CaO5/Lv0PARAkF5AJ47hQ9Q19JpEY2nxHwTFzw/DCVA7gCghYzf HbZlVI6Q0H7QHq/RKHEOQTE= =jsKf -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
