Received: by taz.hyperreal.com (8.6.12/8.6.5) id SAA08576;
 Wed, 24 Jul 1996 18:46:10 -0700
Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with
 ESMTP id SAA08570; Wed, 24 Jul 1996 18:46:06 -0700
Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by
 sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id UAA00377 for
 <new-httpd@hyperreal.com>; Wed, 24 Jul 1996 20:46:03 -0500 (CDT)
Message-Id: <199607250146.UAA00377@sierra.zyzzyva.com>
To: new-httpd@hyperreal.com
Subject: Re: per-dir config patch 
In-reply-to: akosut's message of Wed, 24 Jul 1996 16:06:52 -0700.
         <Pine.SOL.3.93.960724155311.1410A-100000@acidik.organic.com>
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 24 Jul 1996 20:46:03 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

> Here's a patch that implements some of the functionality I've been talking
> about the last few days. It does four things:
> 
> 1) Contains the patch I submitted earlier to make <Location> work only on
> directory segments.
> 
> 2) Adds a pregcomp() function to alloc.c (also adds #include
> "regex/regex.h" to conf.h).
> 
> 3) Adds a <Files> directive. This works akin to how I'm given to
> understand the Netscape Server directive of the same name works. It works
> very much like <Directory>, except it applies to all files, not just
> directories. So you can do <Files /some/path/to/a/file.html>. You can also
> put <Files> into an .htaccess file. It supports relative pathnames, so you
> can put <Files file.gif> in /www/.htaccess and it will apply to
> /www/file.gif.
> 
> 4) Allows <Directory>, <Location> and <Files> to use regular expressions
> instead of simple prefix matching or wildcard matching. The syntax is:

Looks great!  I say +1.