> This is indeed the case if Jetty can check that cookies are properly > handled by the client. But on the first access, Jetty has no way to > check that cookies are accepted by the client so it will add the > jsessionid automatically. This is why search engines suffer from this > problem. If you use a tool such as Webmaster (from Google) you'll see > that a lot of indexed urls come with the jsessionid and they might end > up in the search results displayed to users (altough I believe this is > not any more the case).
Ok, I have learned something new today :) You will only have this problem if you are creating a user session for each and every request. If you are a bit more conservative for creating user sessions (for example, storing data in cookies for the anonymous user) maybe this issue would disappear. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
