config/5214: Feature request - better error messages

[c h <ge...@usa.net>]

>Number:         5214
>Category:       config
>Synopsis:       Feature request - better error messages
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Thu Oct 28 11:50:01 PDT 1999
>Last-Modified:
>Originator:     geek6666@usa.net
>Organization:
apache
>Release:        1.3.9
>Environment:
Any
>Description:
> [Thu Oct 28 10:11:34 1999] access to /home/firewall/HTML/admin/ 
>  failed for 10.10.10.46, reason: Directory index forbidden by rule

The problem: I can't easily find the rule that caused this.
>How-To-Repeat:
Create an .htaccess file that denies access to a file.
Hide it in the directory tree leading up to the file.
Try and find it.
>Fix:
New error message: 
 "...reason: Directory index forbidden by rule /home/firewall/.htaccess line 7"

While reading config files, .htaccess files and whatnot, record the filename
and line number.  When a rule is violated, log which rule.

For extra credit, create a command line debug flag that logs the rules used
for each request, or the first 10 requests, or the first request that matches
a regex.

For extra-extra credit, allow debugging of a cgi program with strace, running
strace only once for the given cgi.

Thanks!
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]