-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg,
Gregory Gerard wrote:
| A follow up question for 100: why does the spec define this at all
I think they explicitly set the session id parameter and cookie name
so that different implementations would be compatible. In some cases,
you may need
There usually isn't much happiness in the spec violations. Most of the
time, the violations are due
- optimizations
- contradictions
- better use case where not following the spec is a good idea (but in
those cases, the ability to follow the spec is still there)
-Tim
Gregory Gerard wrote:
thanks,
greg
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm not sure whether you mean the cookie or the URL parameter, but the
answer is the same in both cases: Change the constant in the code and
re-compile Tomcat. There's no other way that I can see.
--
Len
On Feb 6, 2008 10:15 PM, Gregory Gerard [EMAIL PROTECTED] wrote:
thanks,
greg
that fits with what I saw as well.
A follow up question for 100: why does the spec define this at all and
why does Tomcat not let me work around it when it happily lets me
violate other parts of the spec?
greg
Len Popp wrote:
I'm not sure whether you mean the cookie or the URL parameter,
