Received: by taz.hyperreal.com (8.6.12/8.6.5) id LAA15233; Wed, 17 Jul 1996 11:03:44 -0700 Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id LAA15226; Wed, 17 Jul 1996 11:03:40 -0700 Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id NAA07105 for ; Wed, 17 Jul 1996 13:03:40 -0500 (CDT) Message-Id: <199607171803.NAA07105@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: Authentication API In-reply-to: rst's message of Wed, 17 Jul 1996 13:35:53 -0400. <199607171735.NAA30503@skydive.ai.mit.edu> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jul 1996 13:03:40 -0500 From: Randy Terbush Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > > Ummmm... there are several ways this could be done, and it's impossible > > to say what would be best without knowing *why* you want this. What > > problem are you trying to solve? > > I would like to have access in the request_rec to information > regarding Access control and active Options for a given URL. > > I hate to repeat myself, but I have to. Why do you want this > information? What problem are you trying to solve? (You said what > information you want the first time. I'd like to know why you want > it. To repeat myself again, there are a bunch of different ways to > get at it, and which is best will really depend on what you are trying > to do --- and just saying "get access to this information" obviously > doesn't discriminate among the choices). > > rst I would like to provide an interface to allow editing/configuring of these per_directory controls.