-
1. Re: ;JSESSIONID vs ;jsessionid (jboss3.0.3)
Funny, my copy of the spec (servlet 2.4) says :
SRV.7.1.1 Cookies
Session tracking through HTTP cookies is the most used session
tracking mechanism and is required to be supported by all servlet
containers. The container sends a cookie to the client. The client
will then return the cookie on each subsequent request to the server,
unambiguously associating the request with a session. The name of the
session tracking cookie must be JSESSIONID.
What version of mod_jk ?
Mine works fine.
Jules -
2. Re: ;JSESSIONID vs ;jsessionid (jboss3.0.3)
I mean when URL encoding the session information, when cookies aren't used.
From the spec:
SRV.7.1.3 URL Rewriting
URL rewriting is the lowest common denominator of session tracking. When a client will not accept a cookie, URL rewriting may be used by the server as the basis for session tracking. URL rewriting involves adding data, a session id, to the URL path that is interpreted by the container to associate the request with a session.
The session id must be encoded as a path parameter in the URL string. The name of the parameter must be jsessionid. Here is an example of a URL containing encoded path information:
http://www.myserver.com/catalog/index.html;jsessionid=1234
--
Jetty would make this URL:
http://www.myserver.com/catalog/index.html;JSESSIONID=1234
mod_jk (a very recent version, I compiled from source only a week ago) only looks for ;jsessionid, as per the spec, and gets confused by ;JSESSIONID. -
3. Re: ;JSESSIONID vs ;jsessionid (jboss3.0.3)
The changes are in CVS (jboss-3.2).
They will be rolled into the next 3.0 release.
If you want to run them with 3.0, checkout HEAD of Jetty cvs (from SourceForge), build it and use the jars from this in place of the ones in yout jbossweb.sar.
Thanks for spotting this,
Jules