Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 17179 invoked from network); 6 Feb 2004 15:23:21 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Feb 2004 15:23:21 -0000 Received: (qmail 56576 invoked by uid 500); 6 Feb 2004 15:23:04 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 56506 invoked by uid 500); 6 Feb 2004 15:23:04 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 56481 invoked from network); 6 Feb 2004 15:23:03 -0000 Received: from unknown (HELO Boron.MeepZor.Com) (204.146.167.214) by daedalus.apache.org with SMTP; 6 Feb 2004 15:23:03 -0000 Received: from apache.org (dmz-firewall [206.199.198.4]) by Boron.MeepZor.Com (8.11.6/8.11.6) with ESMTP id i16FN6L11038; Fri, 6 Feb 2004 10:23:06 -0500 Message-ID: <4023B0F6.10505@apache.org> Date: Fri, 06 Feb 2004 10:21:26 -0500 From: gregames@apache.org User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en MIME-Version: 1.0 To: httpd , Geoffrey Young Subject: Re: [PATCH] configurable Location block speed up References: <4021669F.1060904@apache.org> <40226E22.80005@modperlcookbook.org> In-Reply-To: <40226E22.80005@modperlcookbook.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N moving to dev@ ... this deserves wider attention IMO Geoffrey Young wrote: > one thing I was wondering about was the interaction between your patch an > mod_alias. just by following the code without testing, it seems like either > mod_alias needs to unset the outside_filesystem flag for things like Alias > and ScriptAlias, something like that might work > or it needs to blow up over the conflict between those directives and your new directive. or Joshua's "virtual" keyword on , which I like better the more I think about it. But yeah, good point. Unfortunately it adds complexity. If the conflict could be detected at config time rather than run time, the added complexity does't bother me much at all. > that is, unless I'm reading the code wrong, or common setups like this > > Alias /cgi-bin /usr/local/apache/cgi-bin > > SetHandler cgi-script > ... > > > are also ones that you believe go against the existing documentation. > > anyway, not a criticism (especially if I'm wrong), I think you're right. Constructive critism is always welcome :) > just an observation. > --Geoff No problem... excellent feedback. Greg