Return-Path: owner-new-httpd
Received: by taz.hyperreal.com (8.6.12/8.6.5) id IAA22666;
 Tue, 8 Aug 1995 08:57:14 -0700
Received: from life.ai.mit.edu by taz.hyperreal.com (8.6.12/8.6.5) with SMTP
 id IAA22651; Tue, 8 Aug 1995 08:57:11 -0700
Received: from volterra (volterra.ai.mit.edu) by life.ai.mit.edu (4.1/AI-4.10)
 for new-httpd@hyperreal.com id AA27739; Tue, 8 Aug 95 11:57:02 EDT
From: rst@ai.mit.edu (Robert S. Thau)
Received: by volterra (4.1/AI-4.10) id AA29071; Tue, 8 Aug 95 11:57:00 EDT
Date: Tue, 8 Aug 95 11:57:00 EDT
Message-Id: <9508081557.AA29071@volterra>
To: new-httpd@hyperreal.com
Cc: new-httpd@hyperreal.com
In-Reply-To: <9508072019.AA05598@www.elsevier.co.uk> (message from Andrew
 Wilson on Mon, 7 Aug 95 21:19:57 BST)
Subject: Re: ErrorDocument control from .htaccess files...
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

   Date: Mon, 7 Aug 95 21:19:57 BST
   From: Andrew Wilson <andrew@www.elsevier.co.uk>

   [ Notes that ErrorDocument can be made to work in .htaccess files
     simply by changing the overrides mask in the core command table
     which says it isn't allowed there... ]

   1) All this is to be expected, but am I going over the top by choosing
   OR_ALL?  Could I make do with a more restrictive OR_? (there isn't one
   specific enough)

OR_ALL is going way overboard --- you're saying that if *anything* can
be overridden, then ErrorDocuments can be overriddent as well.  What's
really needed here, as you suggest, is a new AllowOverrides option,
but we're outta bits in the bit mask (0.8.x inherits eight-bit
override masks from the old code base).

rst