Andy, you can strip the session id with filter, but you should also check if the pages you want index really need to be stateful. When your servlet container adds a session id, it means it found it necessary to create a session. If you just strip the session id, a new session will be created for every request from a search engine crawler, which is usually not want one wants, especially if you have a lot of pages.
Tapestry makes it easy to make your pages stateless, since ASOs are not created before they are used, and you can check for existence before using (and thereby creating) them. That will also solve the session id issue, since for the stateless pages, a session won't even be created. Have you thought about that? hth, Lutz On Tue, Dec 30, 2008 at 5:13 PM, Andy Huhn <amh...@hslt-online.com> wrote: > Hello, > > I'm having issues with the way my app is being crawled by search > engines. A jsessionid parameter is being added to the URL of each > request, making the link obtained by the search engine useless. > > I'm running Jetty 6. I know from perusing the web that this jsessionid > is being added by Jetty, but I don't know how to disable that, other > than writing a ServletFilter > ( http://mail-archives.apache.org/mod_mbox/tapestry-users/200606.mbox/% > 3c85ce4e3fd2ec2c4e8aae39916ac1a3830f9bc...@ms07.mse2.exchange.ms%3e ). > This is something I'd rather not get into. Any suggestions? Or does > anyone have any working T5 code I could plug in that would take care of > this for me? > > Thanks, > Andy > > -- altocon GmbH http://www.altocon.de/ Software Development, Consulting Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
