On Fri, 10 Sep 2010, Sergio Junqueira wrote:
I have a suggestion for the developers of Apache related to mod_log_config or
mod_log_forensics:
1) To allow mod_log_config to write the log file with a first log entry with
basic information about the request before it's processed further (that is,
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
On 05 Sep 2010, at 7:05 PM, Ruediger Pluem wrote:
Nitpicking: IMHO we are changing a public API. Where is the minor
bump?
Thanks for the catch, it's in r996311.
Regards,
Graham
--
On 06 Sep 2010, at 11:00 PM, Paul Querna wrote:
Isn't this problem an artifact of how all bucket brigades work, and is
present in all output filter chains?
An output filter might be called multiple times, but a single bucket
can still contain a 4gb chunk easily.
It seems to me it would be
Hi all,
The CacheMinFileSize and CacheMaxFileSize directives in mod_disk_cache
are currently set per server, which seems to be historical from the
time before mod_cache could be added as a normal handler /
specifically placed filter. This stops an administrator applying a
cache size
Do you need the first entry to determine which request may have caused httpd
to
crash or is there a different reason?
Mod_log_forensics writes the log record as soon as it is received.
Mod_log_config writes the log record after the response is available. I don´t
want to miss information about
I'm not sure it is related, but I'd like to know the most efficient way
to debug error_log entries such as the following. In the first case, I
presume that the referrer was absent or was unable to be read.
Ideally a conditional forensics log (i.e. only on error response codes)
would probably
