If you don't need session management, use the JSP page directive to turn
off sessions -- at least until the user logs in, if you have that kind
of website. The jsessionid is only for a stateful application, so if you
don't need sessions, get rid of them. That will solve your problem.
Paul
Ed Griebel wrote:
http://www.junlu.com/msg/287317.html
As stated in above response to (your) similar question, the first
request that is returned will have jsessionid= appended. To get rid of
it you can try having the first page of the application be a "dummy"
page that merely redirects to the real page.
The reason why the jsessionid is appended the first time is that the
web server cannot know _a priori_ if a browser has enabled cookies.
Only when the web server gets a second request from the browser with a
jsession id cookie can it assume that it has cookies and will strip
the jsessionid from future requests.
-ed
On 10/4/06, sunil virmani <[EMAIL PROTECTED]> wrote:
Hi All,
In my application in each request jsessionid is passed both in cookie as
well as in url. I have enabled the cookie then why it is appearing in the
URL also.
Regards,
Sunil
---------------------------------------------------------------------
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]
