I took the sources of the 5.0.30 tomcat and made the changes, recompiled
the RPM and installed it on one of my QC servers .
the session id that is generated from the tomcat is indeed 30 chars but
now it seems that the jvmroute and the balancer in front of it are not
adding the .x to the
Assaf Flatto wrote:
I took the sources of the 5.0.30 tomcat and made the changes, recompiled
the RPM and installed it on one of my QC servers .
the session id that is generated from the tomcat is indeed 30 chars but
now it seems that the jvmroute and the balancer in front of it are not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Assaf,
Assaf Flatto wrote:
now it seems that the jvmroute and the balancer in front of it are
not adding the .x to the jsessionid.
[snip]
but the end result is cookie:
JSESSIONID=FB5B5218F8A9021652FDE8C270F991
Perhaps the proxy module is
Hello
Does anyone know how i can shorten the length of the jsessionid from 32
chars to 30 ?
thanks
Assaf
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Assaf,
Does anyone know how i can shorten the length of the jsessionid from 32
chars to 30 ?
In Tomcat 4.1, the class org.apache.catalina.session.ManagerBase creates
sessions and assigns ids to them. The source I'm looking at right now
uses a message digest algorithm (it's not clear which one,
Assaf Flatto [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello
Does anyone know how i can shorten the length of the jsessionid from 32
chars to 30 ?
Set sessionIdLength=15 on the Manager / tag for your context.
thanks
Assaf