I suggest you use Firefox and a little plug-in called LiveHttpHeaders,
that way you can see what JSESSIONID cookie is sent up to the server
from your browser, and this will help you figure out what is wrong
Filip
csp wrote:
On 2/25/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
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/
Sorry, was out of town all these times.
No, actually, not exactly that.
I have server S1
http://s1.test.com:8080/
and server S2
http://s2.test.com:9090/
If I set the two servers to use the same port number, everything is ok. But
if I set them
to use different port numbers, it is totally wacky. When the user is
redirected from S2 to S1, I always get a new session on S1, even though the
user has already a session on S1.
But if I set the two servers to use the same port number, when the user is
redirected
from S2 to S1, I always get back the same session on S1.
This is totally weird.
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
