> 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.
Yes, I agree, but in my case I could find anywhere in my code where I was creating a Session (maybe it was done in another layer, I am using the Stripes as a framework - which I really recomment.) But I would have expected that disabling the session in app engine would also remove the jsessionid from the url. However that was not the case. And same thing with the jetty configuration parameters. So a filter to wrap the response was the only solution I found. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
