https://bz.apache.org/bugzilla/show_bug.cgi?id=60681

--- Comment #7 from William A. Rowe Jr. <wr...@apache.org> ---
Flipping this back is the wrong course of action.

The purpose of the error log is to alert and advise the operator or content
maintainers of the server of those conditions under their control which can
be fixed to improve delivery of content. This can include not-found requests
(which might reflect now-missing content or bad redirects between content),
failing misdirected back-end proxy requests, server load fault conditions
and other problem cases that demand the operator's attention.

No malformed request can be addressed by the server operator, these represent
an error by the client/user agent which need to be addressed by the user.
In some cases the user is the operator, which is why all of the malformed
requests can be more carefully examined at core loglevel debug.

The specific feature request noted by reporter is that some administrators 
would like to scrape log files for invalid requests, in order to add those 
remote ip addresses to lower-level ban lists. (There is no efficiency to
adding those ip addresses to any application-level httpd ban module because 
these errors are dispatched almost immediately before the request processing
phases begin.)

This request is already possible today with no change to httpd by scraping
the access log for any 400 responses. All 400 responses indicate a malformed
request, whether this is a malformed request line or header line, or some
invalid header values.

Other client-originated errors, such as not-found, auth required, etc will
all fall into an error code >400 <500.

For all httpd operators who were not using the error log to effect some
ban list, changing the severity will simply generate unactionable, and
therefore wasteful log file bytes.

I'd vote WONTFIX.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

Reply via email to