Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 32252 invoked by uid 500); 22 Jul 2002 04:20:12 -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 32238 invoked from network); 22 Jul 2002 04:20:10 -0000 X-Curiosity: Killed the Cat X-Huis-aan-Huis-deur-sticker: nee-nee X-Spam: no X-Passed: MX on Gandalf.WebWeaving.org Sun, 21 Jul 2002 21:20:14 -0700 (PDT) and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Date: Sun, 21 Jul 2002 21:20:09 -0700 (PDT) From: dirkx@covalent.net X-X-Sender: dirkx@mobile.webweaving.org To: dev@httpd.apache.org Subject: Re: httpd-2.0 and Auth*Authoritative In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I have often spoke of having a per directory/location ordering of auth > handleres. This would allow you to load a bunch of auth handler modules, > then in a given directory elect which ones are run, and what order they > run in (and the last one would be assumed authoritatve perhaps). That would be -very- usefull. And not just for auth - also for modules rewriting. So perhaps a per hook order control. Of course there are some chicken egg issues with this ! Dw.