Rainer Jung wrote:
Hmmm. Unfortunately I couldn't follow the thread earlier.
As far as I know the problem is the following:
A semicolon is used to separate the jsessionid in case you are using
URL encoded sessions. As far as I remember the AJP connnector does
*not* recognize %3Bjsessionid. So if you are using URL encoded
sessions, semicolons need to be decoded before sending to Tomcat, or
Tomcat needs a patch to recognize %3bjsessionid in the AJP connector.
Of you don't use URL encoded sessions, you can choose the correct
forward option in mod_jk.
That's great in mod_jk -- and as I noted we're already using an
appropriate forward option where we use mod_jk. [This is for conveying
information in the path info -- not for jsessionid, where we require
cookies.]
Concerning mod_proxy_ajp: I'm not sure, if it is a bug. Since %3B and
semicolon should be euivalent, my question is: do you get the correct
path info if you use Tomcat http connector directly and use semicolon
instead of %3B?
";" is not the same as %3B as I understand it. A raw ";" is reserved by
the RFC and denotes a separation between path components and other data,
e.g. jsessionid.
An encoded ";", i.e. %3B should be able to be part of the path
components, though.
As Mark Thomas helped me to realize the issue is that mod_proxy_ajp has
no equivalent of the option we'd been relying upon in mod_jk to resolve
this issue. That's a serious gap in mod_proxy_ajp. On the other hand,
there's a lot to be said for Apache 2.2 in general and mod_proxy_ajp in
particular, so we really need this gap closed and can't just revert to
mod_jk.
--
Jess Holle
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
