Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 84056 invoked by uid 500); 9 May 2003 18:33:53 -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 83955 invoked from network); 9 May 2003 18:33:52 -0000 Date: Fri, 9 May 2003 14:33:55 -0400 (EDT) From: Rich Bowen To: dev@httpd.apache.org Subject: Re: 403's not getting logged? In-Reply-To: <200305091806.h49I66X20481@devsys.jaguNET.com> Message-ID: References: <200305091806.h49I66X20481@devsys.jaguNET.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 9 May 2003, Jim Jagielski wrote: > Rich Bowen wrote: > > > > I'm experiencing a should-not-happen condition in apache 1.3.27, and > > wondered if anyone else could verify for me. In the case of a 403 > > error caused by incorrect directory permissions, there is no error > > log entry. If the file is unreadable, the 403 goes in the error log. > > But if the directory has bogus permissions, there's no entry. > > This is on 1.3.27 I've tested this on 2 servers so far, and it seems > > consistent. > > > > That's as designed, IIRC, though I cannot recall *why* we did it > that way... Then I would suggest that it is a bad design, and leads to a lot of user confusion. Unless there's a really good reason for this, it would be nice to have an error message. -- Rich Bowen - rbowen@rcbowen.com http://kenya.rcbowen.com/