Hi,

this turns out to be a bug indeed. In fact, it has already been reported 
to Bugzilla as 21561. Thanks to that bug report which pointed me to the 
right file I could track down this problem and attached a patch to fix 
it. In jk/native2/common/jk_uriEnv.c:

--- old_jk_uriEnv.c     2003-11-24 13:43:30.000000000 +0100
+++ jk_uriEnv.c 2003-11-24 14:13:16.000000000 +0100
@@ -445,6 +445,7 @@

     if (uri[strlen(uri) - 1] == '*') {
         /* context based /context/prefix/ASTERISK  */
+        uri[strlen(uri) - 1] = '\0';
         uriEnv->suffix      = NULL;
         uriEnv->prefix      = uri;
         uriEnv->prefix_len  =strlen( uriEnv->prefix );


CU,
Stefan


On Monday 24 November 2003 10:10, Dionisio Ruiz de Zarate wrote:
> i have the same problem. i must to downgrade to the 4.1.27 version.
> there is other problem; if you have one dir with, for example, images,
> you must to map the directory.
>
> [uri:/erfx/*]
>  worker=ajp13:localhost:9602
>  context=/erfx
>  tomcatId=localhost:9602
>
> [uri:/erfx/images/*]
>  worker=ajp13:localhost:9602
>  context=/erfx
>  tomcatId=localhost:9602
>
> in other form doesn't run.
> in the 4.1.27 version you dont have to mapp the subdirectories.
>
> > Hi,
> >
> > I've encountered a strange problem which occurred after updating from
> > mod_jk2 compiled from the jakarta-tomcat-connectors-4.1.27-src.tar.gz
> > distribution to the new version from
> > jakarta-tomcat-connectors-4.1.29-src.tar.gz. I have the following
> > workers definition in workers2.properties:
> >
> > [channel.socket:localhost:9602]
> > info=Ajp13 forwarding over socket
> > debug=0
> > host=localhost
> > port=9602
> > tomcatId=localhost:9602
> >
> > [ajp13:localhost:9602]
> > channel=channel.socket:localhost:9602
> > tomcatId=localhost:9602
> >
> > [uri:/erfx/*]
> > worker=ajp13:localhost:9602
> > context=/erfx
> > tomcatId=localhost:9602
> >
> > This works fine with the mentioned mod_jk2 from tomcat 4.1.27.
> > However, with 4.1.29 only the uri /erfx/ gets mapped as expected but
> > /erfx/foo.jsp for example doesn't, i.e., the request is not processed
> > by tomcat but the file is delivered in its raw form by apache. When I
> > add another explicit mapping [uri:/erfx/foo.jsp] it works again. It
> > seems the "*" in the uri no longer works from some reason. Similarly,
> > when requesting an uri which does not directly correspond to a JSP
> > but should be passed to a servlet, I get a 404 (not found) from
> > apache.
> >
> > I'm running Apache 1.3.29 with Tomcat 4.1.29 on a Linux host. As
> > already stated, the same configuration works fine when using the
> > mod_jk2 from the 4.1.27 connector sources. Could someone please shed
> > some light on this and tell me how to get the new mod_jk2 to work?
> > Thanks in advance.
> >
> >
> > CU,
> > Stefan
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to