It's not a bug. When session is first created, Tomcat can't know if cookies are supported or not, so it tries both cookies and URL rewriting. If, on the subsequent request, the session ID comes out of the cookie, Tomcat will stop rewriting the URLs.
jeff -----Original Message----- From: Henri Dupre [mailto:[EMAIL PROTECTED] Sent: Friday, June 16, 2006 9:19 AM To: Tapestry users Subject: Re: Remove jsessionid from static resources? On 6/16/06, D&J Gredler <[EMAIL PROTECTED]> wrote: > > Can you get banned from Google for this? I seem to remember they want to > be > served exactly the same content that a regular useragent would get. > Obviously this isn't the kind of stuff they're trying to avoid... Just > wondering. It is actually more somekind of Tomcat bug I believe... Tomcat is supposed to send a cookie and then not use the jsessionid but for some reasons, it does it anyway. Thanks, Henri. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
