The very first time one accesses an application, session ID is in the address. So, for the first bookmarkable page you have two addresses, which screws up the browser history navigation.
The simple answer: do one more redirect on first request. The more complex answer: do one more redirect when you see that jsessionid in in the URL. The hardest thing: to distinguish that jsessionid is in the URL. See this discussion for relevant information: http://marc.theaimsgroup.com/?l=struts-user&m=111886657513840&w=2 Michael. On 11/8/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > There is no way for Wicket to remove jsessionid (at least no legal > way). It's your servlet container that appends it. When you support > cookies however, there should be no need to encode this id in the url, > and I think some servlet engines don't append it if this is the case. > > Eelco > > > On 11/8/05, pepone pepone <[EMAIL PROTECTED]> wrote: > > Hello all > > > > when i load the firs page browser is redirected to a url that is like > > > > /app;jsessionid=12324?path=1 > > > > there are any way to be redirected to samething like > > > > bookmarkablePage=HomePage > > > > thanks in advantage ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
