tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: cvs commit: jakarta-tomcat-connectors/jk/native/common jk_uri_worker_map.c
Date Fri, 17 Dec 2004 21:27:56 GMT

----- Original Message -----
From: "Mladen Turk" <>
To: "Tomcat Developers List" <>
Sent: Friday, December 17, 2004 12:47 PM
Subject: Re: cvs commit: jakarta-tomcat-connectors/jk/native/common

> Bill Barker wrote:
> >
> > Try with only:
> > JkMount /myapp/*.jsp
> >
> > and requesting:
> > http://myserver//myapp/index.jsp
> >
> Yes I did, and it really doesn't mater.
> Well my jsp's are inside tomcat application, so I admit
> there can be problems if the .jsp is hanging around
> somewhere outside web application :).

It's for when you want Apache to act as the default servlet, so you have:
  Alias /myapp/ /path/to/myapp/
  JkMount /myapp/*.jsp ajp13

> Also I've tried that with 5.0/5.5, so if it breaks
> some older tomcat versions feel free to include the
> jk_no2slash checking again, and compare every char
> with the slash in the uri on the each request made.

All of the Tomcat mappers from 3.3 up will handle the request fine if it
ever sees it.  However,  with the code as it is now, mod_jk will refuse the

Now that mod_jk is hopelessly broken, I guess I'll just have to wait for
proxy_ajp before upgrading.

> Regards,
> Mladen.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message