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:
t
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://m
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 redir
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 o
