Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 2833 invoked from network); 5 Jun 2004 14:29:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Jun 2004 14:29:38 -0000 Received: (qmail 96446 invoked by uid 500); 5 Jun 2004 14:29:31 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 96389 invoked by uid 500); 5 Jun 2004 14:29:31 -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 96372 invoked by uid 99); 5 Jun 2004 14:29:31 -0000 Received: from [66.111.4.26] (HELO out2.smtp.messagingengine.com) (66.111.4.26) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 05 Jun 2004 07:29:31 -0700 X-Sasl-enc: 9SheIUU8taJMaLxECIPy3w 1086445755 Received: from bronfman504 (Toronto-HSE-ppp3741270.sympatico.ca [67.68.68.141]) by mail.messagingengine.com (Postfix) with ESMTP id 78A3AC038B0 for ; Sat, 5 Jun 2004 10:29:15 -0400 (EDT) Date: Sat, 5 Jun 2004 10:29:13 -0400 (Eastern Daylight Time) From: Joshua Slive To: dev@httpd.apache.org Subject: Re: Better error logging for mod_access In-Reply-To: <40C1D64D.6080107@attglobal.net> Message-ID: References: <1086444535.40c1d3f78e08b@correo.speedy.com.pe> <40C1D64D.6080107@attglobal.net> X-X-Sender: slive@fastmail.fm@mail.messagingengine.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Sat, 5 Jun 2004, Jeff Trawick wrote: > ricilake@speedy.com.pe wrote: > > > The patch here: for > > 2.0.49 creates logs that look like this: > > > > [Fri May 28 22:19:16 2004] [notice] Apache/2.0.49 (Unix) configured -- > > resuming > > normal operations > > [Fri May 28 22:19:24 2004] [error] [client 192.168.1.33] client denied by > > order directive at line 362 of /opt/apache2/conf/httpd.conf for: > > /opt/apache2/htdocs/bar > > What about enabling via a per-dir directive? Looks very useful, but some sites > might have a significant number of new entries in error log serving no useful > purpose (for them). The problem with per-dir is that the user might not know exactly where in the config file he should be editting. If they did, they probably wouldn't have a problem finding the relevant allow/deny in the first place. What about keeping the old error message, but logging an *additional* message at loglevel debug with the additional info? Two other notes: - Personally, I hate arbitrary path-size limitations. They always bite you when you least expect it. What about dynamically sizing this? - You'll get more people to read your patches if you use "diff -u". Joshua.