App servers HAVE to put that in the first URL, because it's really the
second (because of the redirect). The server doesn't know if the
client is using cookies until the first request comes back, so for the
first request it has to use cookies and url rewriting.
Why? It's part of the default header info whether a client accepts
cookies or not isn't it?
Eelco
On 11/12/05, Phil Kulak [EMAIL PROTECTED] wrote:
App servers HAVE to put that in the first URL, because it's really the
second (because of the redirect). The server doesn't know if the
client is
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
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,
No, I am not sure for all appservers, so I decided to abandon the
attempts for the most perfect URL ;-)) Because there will be only one
address which is screwed up after all, so I really don't care much (or
so I convinced myself).
I would say to pepone, forgeddaboudid ;-)
Michael.
On 11/8/05,
