I ran into the same problem, and have been unable to find a straightforward solution...you'd think this behavior would be configurable. In the end, we wrote a simple servlet filter that prevents URL rewriting (wraps HttpServletResponse with an object that overrides the encoding functions with no-ops) based on the user-agent string. I found the technique with some Google searching.
jeff -----Original Message----- From: Detlef Schulze [mailto:[EMAIL PROTECTED] Sent: Monday, December 19, 2005 10:40 AM To: Tapestry users Subject: Running stateless Hi, I have an application that runs on tapestry 3 and jetty 4. On the first page that requries a http session the urls are rewritten to enable use of the session, if I navigate to other pages the "jsessionid" isn't there anymore. I assume that this is because at session creation time it is not known wether the client accepts a cookie to store the session id or not. This causes some trouble with google, since it does not like the jsession param. Does anybody know how to disable this behaviour? In other words how can I configure that url rewriting is not used and only session cookies are used ? I am not sure if this is a tapestry or jetty issue, so plese accept my aplologies if I am posting to the wrong list ... Cheers, Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
