Your servlet container adds the jsessionid parameter to the URL if the container thinks, that the browser may not allow cookies. This is typically the case for the first request for which the client doesn’t include a cookie.
Sure, if a browser doesn’t allow/support cookies, the servlet container typically falls back to appending jsessionid to the URL. If you configure the servlet container to don’t behave this way (because you don’t want jsessionid in your URL), the container will of cause not be able to track sessions for such users anymore.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic.
Comments are closed.
Get updates from OCPSoft
If you find our tools useful, please consider making a donation to help us stay online and building software!