hi there!
the original e-mail of craig dates some months back.
> When a session is first created, Tomcat has no way to know whether
> session cookies are supported by the browser. Therefore, to be safe, it
> sends the session ID both ways (by cookie and by modifying URLs that you
> submit to response.encodeURL calls). On subsequent requests that are
> part of this session, Tomcat will notice that it received the session ID
> via a cookie, so it will stop doing the rewriting.
i wonder whether anything has changed here, especially whether there is a
configuration option (possibly in server.xml) that switches cookies for
session tracking of.
thanks a lot
robert
--
Robert Klemme
Software Engineer
-------------------------------------------------------------
myview technologies GmbH & Co. KG
Riemekestraße 160 ~ D-33106 Paderborn ~ Germany
E-Mail: mailto:[EMAIL PROTECTED]
Telefon: +49/5251/69090-321 ~ Fax: +49/5251/69090-399
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
