Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 96275 invoked from network); 10 Aug 2002 08:21:30 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Aug 2002 08:21:30 -0000 Received: (qmail 9140 invoked by uid 97); 10 Aug 2002 08:22:00 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 9092 invoked by uid 97); 10 Aug 2002 08:22:00 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 9080 invoked by uid 98); 10 Aug 2002 08:21:59 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: RE: uri_map using regex [WAS: mod_jk, mod_jk2 URI spaces] From: Bojan Smojver To: Tomcat Dev List In-Reply-To: <002e01c24037$ae7a6130$5c00000a@GISDATA.ZG> References: <002e01c24037$ae7a6130$5c00000a@GISDATA.ZG> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 10 Aug 2002 18:25:49 +1000 Message-Id: <1028967949.1180.29.camel@beast.rexursive.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I think I understand what you're saying here and it will probably be necessary for non-Apache web servers anyway. I was thinking more along the lines of: 1. Anything you want to disallow for TC, rewrite to Apache visible filenames and/or URL's (in your example, image files). Apache will then happily serve them. 2. Anything else, rewrite to URL that match something that's in mod_jk's space. Bojan On Sat, 2002-08-10 at 16:31, Mladen Turk wrote: > > -----Original Message----- > > From: Bojan Smojver [mailto:bojan@rexursive.com] > > Sent: Saturday, August 10, 2002 2:04 AM > > To: Tomcat Dev List > > Subject: Re: uri_map using regex [WAS: mod_jk, mod_jk2 URI spaces] > > > > > > Doesn't mod_rewrite do what you want here? In combination > > with mod_proxy, it can rewrite URL to URL as well, so you can > > get the resulting URL back in mod_jk and then just use normal > > mappings. Or maybe I'm on a totally wrong track here... > > > > True (I think) for the positive assertions, but: > > [uri:/examples/*] > #matches entire app > > [uri:/examples/(?!\.(gif|jpe?g|png)$)] > #matches everything except .gif, .jpg, .jpeg, .png > > The entire purpose is to be able to _disallow_ certain mappings in the > already mapped application. > I'm afraid that the mod_proxy cannot be used for such a thing, cause the > first mapping will forcibly drive all the examples context through the > TC. > At first I was trying (before the pcre idea) to use the simple matching > like : > > [uri:/examples/*] > > [uri:!/examples/*.jpg] > > ...etc > > This is can be parsed without using pcre (using apr_fnmatch), but what > about more complex schemas involving directories and file extensions, > not only files. > On the other hand, we can use the mod_rewrite/mod_proxy only with the > Apache, and we want to be portable thought. > > MT. > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: