Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 2384 invoked by uid 6000); 11 Jul 1998 19:41:41 -0000 Received: (qmail 2373 invoked from network); 11 Jul 1998 19:41:37 -0000 Received: from eastwood.aldigital.algroup.co.uk (194.128.162.193) by taz.hyperreal.org with SMTP; 11 Jul 1998 19:41:37 -0000 Received: from freeby.ben.algroup.co.uk (freeby.ben.algroup.co.uk [193.133.15.6]) by eastwood.aldigital.algroup.co.uk (8.8.8/8.6.12) with ESMTP id TAA24432 for ; Sat, 11 Jul 1998 19:40:41 GMT Received: from algroup.co.uk (naughty.ben.algroup.co.uk [193.133.15.107]) by freeby.ben.algroup.co.uk (8.6.12/8.6.12) with ESMTP id UAA19078 for ; Sat, 11 Jul 1998 20:40:34 +0100 Message-ID: <35A7BF9A.ED04812@algroup.co.uk> Date: Sat, 11 Jul 1998 20:40:10 +0100 From: Ben Laurie Organization: A.L. Group plc X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: Confusion: run_method and optimized lists? (Dean?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Dean Gaudet wrote: > > On Sat, 11 Jul 1998, Ralf S. Engelschall wrote: > > > The reason why I didn't discovered this while I've done > > my "grep core_translate" is because Dean calls it via > > > > /* we require other modules to first set up a filename */ > > res = core_module.translate_handler(r); > > if (res == DECLINED || !r->filename) { > > return res; > > } > > > > Shit! In other words: Whenever mod_mmap_static is present (independed if used > > or not!) the complete translation phase comes out of sync because > > mod_mmap_static itself runs the methods again. > > It doesn't run the methods again, it only runs core_translate. > > I thought I had a comment in there saying mod_mmap_static should be the > first module (i.e. lowest priority above core). That's where it's > supposed to be... it's supposed to run after mod_rewrite and mod_alias > have had a chance to translate the filename, not before. > > I'm curious though, the example setup you gave me, does that really enable > mod_mmap_static? It shouldn't be enabled at all in any server by default. This reminds me - do we have a coherent plan for this in 2.0? Coz this messing about with placement in Configuration seems doomed to failure in the long run, IMO, as well as being completely tedious to manage. Apache-SSL has this problem, too. In order to do some of its tricks, it needs to be high-priority. But really, it only needs it for certain phases. I suspect we need to be able to define priority phase-by-phase. Cheers, Ben. -- Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/ and Technical Director|Email: ben@algroup.co.uk | A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/ London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/ WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/