Looking at the first code snippet, it seems that you encode the URL before the session is being created.
The first step in debugging this is to check whether the URL actually contains the session information.
url prints result , not encoded result.but why?
The container should try both cookies and URL rewriting , for the first response it sends.
The container try both cookies and URL rewriting, for the first response it sends. The interest thing here is that, when first request sent to the container, the container creates session object and constructs cookie object by using its session id, name, like
this is what i want - url is result;jsessionid=some id
Did you block / disable the cookies in browser ?
Hi Priya. After blocking the cookies, is url rewriting working?
"Chinmaya Chowdary" wrote:Please check once for the resource
wether 'jsessionid:' appends or not? I tested this in Tomcat5.5.9 and it will not append.