You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/07/14 11:50:34 UTC
DO NOT REPLY [Bug 21561] New: -
jk_uriEnv.c version 1.49 does not handle uri's with asterix
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21561>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21561
jk_uriEnv.c version 1.49 does not handle uri's with asterix
Summary: jk_uriEnv.c version 1.49 does not handle uri's with
asterix
Product: Tomcat 4
Version: Unknown
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Connector:Coyote JK 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: christoph.grimm@db.com
i have checked out and built jakarta_tomcat_connectors at 07/11/2003 (HEAD)
i am only using the native part of the build ( mod_jk2.so ) for apache 2.0.47
the probelem that i am encountering is, that jk2 does not handle uri's like
[uri:/examples/*] or [uri:/jkstatus/*] correctly.
e.g. for the latter one no subcontext can be accessed ( /examples/jsp/ )
but it works if i specify an additional entry [uri:/examples/jsp/*]
the same problem occurs with the jkstatus context so it's definitly a jk2
problem.
Fix:
as a fix i have rolled back the file jk/native2/common/jk_uriEnv.c from version
1.49 to version 1.48. With this change everything worked fine.
I had a briev look a the diff between the versions 1.48 and 1.49 and it seems
to me that the changes made to the uri wildcard handling could be a possible
source for the problem.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org