That's a feature of the application server you're using. It has to put that on there initially because it doesn't know if the browser supports cookies or not. When a subsequent request comes in with the jsessionid cookie, it no longer needs to append it to the URLs. Check the docs for HttpServletResponse.encodeURL():
http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletResponse.html#encodeURL(java.lang.String) On Thu, Mar 27, 2008 at 7:05 PM, Penn <[EMAIL PROTECTED]> wrote: > > Hi, > > when i go to my homepage for the first time, after clearing caching in the > browser, clicking on the login form I see > > > http://localhost:8080/;jsessionid=905AA4A0D7E4441514ED2588160A04E5?wicket:interface=:0:loginform::IFormSubmitListener:: > > After the first time and go back to home page again it is resolved to > > > http://localhost:8080/home?wicket:interface=:1:loginform::IFormSubmitListener:: > > so how to avoid the jessionid in the url for the first time > > Penn > -- > View this message in context: > http://www.nabble.com/how-to-resolve-jsessionid-for-the-first-time-in-the-url-tp16340508p16340508.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
