Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 72203 invoked from network); 31 Jul 2002 21:56:35 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 31 Jul 2002 21:56:35 -0000 Received: (qmail 1839 invoked by uid 97); 31 Jul 2002 21:56:54 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 1814 invoked by uid 97); 31 Jul 2002 21:56:53 -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 1779 invoked by uid 98); 31 Jul 2002 21:56:53 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: RE: mod_jk, mod_jk2 URI spaces From: Bojan Smojver To: Tomcat Dev List In-Reply-To: <002b01c23899$f2c8e8c0$5c00000a@GISDATA.ZG> References: <002b01c23899$f2c8e8c0$5c00000a@GISDATA.ZG> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 01 Aug 2002 08:00:16 +1000 Message-Id: <1028152816.1183.38.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 On Wed, 2002-07-31 at 23:55, Mladen Turk wrote: > > Now I propose that we make something like _not_ URI space > > filtering. Meaning that one could be able to serve every > > .html file through TC except for the /*/some_space/ location. > > Right now we are checking and hoping that the TC will accept > > the context, and then we forget that immediately. I propose > > that we make the map_to_storage two way (If the TC accepts it > > and then checking if the Apache configuration rejects it). This above sentence is confusing. You probably meant configuration options as a series of include/exclude switches, rsync style. > After I read my mail, it doesn't make sense even for me :) > > For example (what I have in mind) using mod_jk: > > JkMount /examples/* > (This will map /examples URI space and everything belonging to the > /examples will be served by the TC). > > JkNotMount /examples/*.gif > JkNotMount /examples/*.jpg > > (This will map /examples URI space and everything will be served by the > TC except the gif and jpg files). I see your point here. You are running a setup where anything not specifically targeted for Apache goes to Tomcat. As long as this doesn't affect current situation (and I don't see how it would) where I can set up that Tomcat only gets what's not specifically targeted for Apache, I'm +1. This would make mod_jk configuration really flexible. Bojan PS. Given 1.2.0 is due for a release when Henri comes back from holidays (in about 2 weeks time), are you planning the patches for this before of after the release? -- To unsubscribe, e-mail: For additional commands, e-mail: