e.html
--
View this message in context:
http://www.nabble.com/Why-can-the-JSESSIONID-name-not-be-changed--tf532684.html#a7713586
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryce,
brycenesbitt wrote:
> Stefan Bethke wrote:
>> Hi,
>> We're currently integrating a couple of web sites under a single
>> domain. Some of the sites run on separate Tomcats, others use PHP,
>> Perl or a number of proprietary systems. We bel
context:
http://www.nabble.com/Why-can-the-JSESSIONID-name-not-be-changed--tf532684.html#a7700835
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubsc
Am 11.11.2005 um 21:14 schrieb George Sexton:
I'd like to understand the rationale for this requirement. If the
container manages the session, why would an application care about
the actual mechanism used to track the session? Why can this not be
made configurable?
I'm guessing the reason its in
ED]
> Sent: Friday, November 11, 2005 3:19 AM
> To: users@tomcat.apache.org
> Subject: Why can the JSESSIONID name not be changed?
>
> Hi,
>
> I hope this is the right list to ask; if not, please direct me to a
> better place...
>
> We're currently integrating a
es of Tomcat and make it configurable
there.
Cheers
Bernhard
> -Ursprüngliche Nachricht-
> Von: Stefan Bethke [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 11. November 2005 11:19
> An: users@tomcat.apache.org
> Betreff: Why can the JSESSIONID name not be changed?
>
&g
Hi,
I hope this is the right list to ask; if not, please direct me to a
better place...
We're currently integrating a couple of web sites under a single
domain. Some of the sites run on separate Tomcats, others use PHP,
Perl or a number of proprietary systems. We believe that having
m
