Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 47640 invoked by uid 500); 9 May 2003 17:41:55 -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 47616 invoked from network); 9 May 2003 17:41:54 -0000 X-Epoch: 1052502115 X-Sasl-enc: 6YhFNiTDisUJQLWoU5uS1Q Date: Fri, 9 May 2003 13:41:16 -0400 (=?ISO-8859-1?Q?Est_=28heure_d'=E9t=E9=29?=) From: Joshua Slive To: dev@httpd.apache.org Subject: Re: 403's not getting logged? In-Reply-To: Message-ID: References: X-X-Sender: slive@www.fastmail.fm 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, 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. Yes, this is a very longstanding and very irritating omission. I don't think I would be exagerating if I said this was the source of hundreds of confused queries to the users mailing list and newsgroup. I browsed through the default handler a while back trying to figure out where this error was getting dropped, but I ran out of time and never got back to it. Someone who knows the code better could probably find it faster. Joshua.