Jess Holle schrieb:
Mark Thomas wrote:
Jess Holle wrote:
Mark Thomas wrote:
I couldn't see anything either. This looks like a mod_proxy_ajp
bug/missing feature.
I jumped the gun once by filing this against Tomcat, but it seems
everything is pointing to mod_proxy_ajp. Is it time to file a bug
against it?
Looks like it to me.
Done. [https://issues.apache.org/bugzilla/show_bug.cgi?id=44803]
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.
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?
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
