Filip Hanik - Dev Lists wrote:
very true, didn't realize so many places referenced it, however, this
gets confusing
-public static final String SESSION_COOKIE_NAME = "JSESSIONID";
+public static final String SESSION_COOKIE_NAME =
+System.getProperty("org.apache.catalina.JSESSION
On Mon, Oct 6, 2008 at 1:54 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> very true, didn't realize so many places referenced it, however, this gets
> confusing
>
> -public static final String SESSION_COOKIE_NAME = "JSESSIONID";
> +public static final String SESSION_COOKIE_NAME =
very true, didn't realize so many places referenced it, however, this
gets confusing
-public static final String SESSION_COOKIE_NAME = "JSESSIONID";
+public static final String SESSION_COOKIE_NAME =
+System.getProperty("org.apache.catalina.JSESSIONID", "JSESSIONID");
/**
Filip Hanik - Dev Lists wrote:
> I don't see an issue with that patch, looks good to me
http://people.apache.org/~jfclere/patches/jsessionid.patch is more complete
but as Remy pointed out it has a couple of issues.
As it happens, I am looking at this now. I'll commit something to trunk and
then p
I don't see an issue with that patch, looks good to me
Filip
André-John Mas wrote:
Hi,
We have recently encountered an issue where running two separate
Tomcat instances behind a single HTTPD server would cause issues with
the JSESSIONID cookie, because each is over-writing the name of the
othe
