general/5200: error_log entries give variable and frankly inadequate information

[Dirk Koopman <dj...@tobit.co.uk>]

>Number:         5200
>Category:       general
>Synopsis:       error_log entries give variable and frankly inadequate information
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Oct 26 11:40:00 PDT 1999
>Last-Modified:
>Originator:     djk@tobit.co.uk
>Organization:
apache
>Release:        1.3.x
>Environment:
Not relevant, but all flavours of Linux, apache 1.3.x
>Description:
I have a website which is under constant attack, it is a bit half hearted at the 
moment (probably because they don't on what it is based) but I want to see clearly
what they a) sent and b) their IP address _IN_EVERY_CASE_. This doesn't happen.

It makes it very difficult to trace who is doing exactly what.

EVERY line in error_log should have a date/time, preferably in exactly the same
format as the access_log and _MUST_ have an IP address and preferably the possibility
of a REFERER URL.

BTW please you put a WRAP=Soft into the <textarea> tags in this bug report form
>How-To-Repeat:
I would prefer not. But try any invalid thing.
>Fix:
Modify the logging module so that you can specify information you always want on the front
of every error_log line? 
>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!     ]