this is what the browser does.
in order for the browser to send the cookie to the server, the URL needs
to be the same.
That is the domain-name/ip, port and path.
so, http://my.server.com:8080/ is different from http://my.server.com:8081/
Filip
coco nut wrote:
I have question about http redirect and the way tomcat manage
sessions. I have two servers, S1 and S2. The user is already
connecting to S1 (I have a session in S1 with the user already), then
he goes to S2 (have a session in S2 as well).
On S2, he clicks on a link which redirects to a page on S1. The issue
here is:
1. If S1 and S2 uses the same port number (e.g. 8080), I can get back
the same session of the user in S1 when I receive the redirect on S1.
2. If S1 and S2 uses different port numbers (e.g. 8080 on S1, and 9090
on S2), when a redirect comes in on S1, I can never get the same
session. I get a totally new session.
Why? What's the issue here? Could someone enlighten please?
Thanks a lot.
coco
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
---------------------------------------------------------------------
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]
