tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: JSESSIONID doesn't contain the port
Date Thu, 19 Jun 2008 16:09:02 GMT

Leon Rosenberg wrote:
> On Thu, Jun 19, 2008 at 5:42 PM, Pid <> wrote:
>> André Warnier wrote:
>>> Leon Rosenberg wrote:
>>>> On Thu, Jun 19, 2008 at 4:51 PM, André Warnier <> wrote:
>>>>> Now, maybe the issue is whether the session of one application can or
>>>>> cannot
>>>>> be valid for the other.  If they just shared a session (and a cookie),
>>>>> then
>>>>> there would be harmony again.
>>>> Or the OP just renames one of his application and all is settled again
>>>> :-)
>>> But that would not change the name of the cookie, or would it ?
>> The problem is that the TC1 sets a value of JSESSIONID that does not exist
>> in TC2.  So when it visits the 2nd app, the session id it presents is not
>> valid.
> yes
>> Changing the cookie name, value or adding a port number will make no
>> difference.
> of course it would since there will be two different cookies with
> different pathes referring to both different sessions.
> wouldn't there?
So now that it is settled that different names for the cookies /would/ 
solve the problem, is that a possibility in Tomcat ?
Is it possible for one application to "influence" the name of it's 
session cookie, so that we could have JSESSIONID-1 and JSESSIONID-2 ?

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message