No. You can supply a patch - but no one will commit it. If it is committed,
the other committers will -1 it.
-Tim
Lasse Koskela wrote:
Any plans on externalizing the session key into an optional
configuration element in server.xml?
Please forgive me if I appear overly persistent but I honestly have no
idea whether Tomcat is strictly required to follow the spec by the
letter and not introduce anything that can be considered extraneous
functionality.
-Lasse-
On Tue, 23 Nov 2004 07:44:15 -0500, Shapira, Yoav <[EMAIL PROTECTED]> wrote:
Hi,
That's still the case in the Spec, yes. So everything Craig said then
is applicable, and your requirement is as bad now as it was years ago.
However, like all other components in Tomcat, you can plug in your own
session manager implementation: you would most likely extend
org.apache.catalina.session.StandardManager. Have fun breaking things
;)
Yoav Shapira http://www.yoavshapira.com
-----Original Message-----
From: Lasse Koskela [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 23, 2004 7:31 AM
To: [EMAIL PROTECTED]
Subject: Changing the default session key
Hello,
I recently encountered a requirement to use a session key other than
JSESSIONID for the cookie of a web application deployed on Tomcat 4
(I'm not yet sure about the exact version).
Now, I found a post from 2002 where Craig said it couldn't be done
(roughly because "JSESSIONID" is defined in the servlet spec and
because Tomcat thus doesn't need to support other session key names).
Is this still the case in 4.x and 5.x?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
