response does not save session id in cookie if it is from url

[zheng li]

i am using tomcat.
if i use jsessionid=617AA28660D5C1B1408543C24B186A75 in url to send session id to server, response does not put it in cookie, so if redirect happens, a completely new session will be created.

is it a bug or http specification?
i can't find anything about it in rfc though.

or is there any configuration about it in tomcat?

[Vijitha Kumara]

Are you saying that you manage the "jsessionid" within your code? Then don't, it's up to the container.

[zheng li]

i am not manage jsessionid myself.
just that i found this problem and don't understand why.

it seems that the two way of managing session id can not coexist.

[Mohamed Sanaulla]

zheng li wrote:i am not manage jsessionid myself.
just that i found this problem and don't understand why.

it seems that the two way of managing session id can not coexist.

Is it not that either URL Rewriting or Cookies are used for session management?

[zheng li]

mohammed sanaullah wrote:

zheng li wrote:i am not manage jsessionid myself.
just that i found this problem and don't understand why.

it seems that the two way of managing session id can not coexist.

Is it not that either URL Rewriting or Cookies are used for session management?

yes, you are right.
thank you.

[Ben Souther]

You don't send the session id to the server. Let Tomcat create them for you.
If there is a session id in the URL and Tomcat can't match it up to an existing session in memory, it just assumes that it is expired and ignores it.