From: Chris Pepper
Date: Tue, 24 Feb 2004 18:58:04 +0000 (+0000)
Subject: Various language nits picked.
X-Git-Tag: pre_ajp_proxy~628
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=922d7cce40923abb9eba6bb0038817f0e6073486;p=thirdparty%2Fapache%2Fhttpd.git
Various language nits picked.
ID consistently uppercased.
Brought in line with 1.3 version.
PR:
Obtained from:
Submitted by:
Reviewed by:
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@102764 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_log_forensic.xml b/docs/manual/mod/mod_log_forensic.xml
index 315d6f0a151..797e5dcd1e3 100644
--- a/docs/manual/mod/mod_log_forensic.xml
+++ b/docs/manual/mod/mod_log_forensic.xml
@@ -30,20 +30,20 @@
This module provides for forensic logging of client
requests. Logging is done before and after processing a request, so the
forensic log contains two log lines for each request.
- The forensic logger works very strict, which means:
+ The forensic logger is very strict, which means:
- The format is fixed. You cannot modify the logging format at
runtime.
- - If it cannot write its data, the particular child process
- exits immediately and possibly dumps core (depends on your
+
- If it cannot write its data, the child process
+ exits immediately and may dump core (depending on your
CoreDumpDirectory
configuration).
- In order to evaluate the log output there's a script
- check_forensic, which can be found in the support directory
- of the distribution.
+ The check_forensic script, which can be found in the
+ distribution's support directory, may be helpful in evaluating the
+ forensic log output.
Apache Log Files
mod_log_config
@@ -55,9 +55,9 @@
where normal logging occurs.
In order to identify each request, a unique request ID is assigned.
- This forensic id can be cross logged in the normal transfer log using the
+ This forensic ID can be cross logged in the normal transfer log using the
%{forensic-id}n format string. If you're using
- mod_unique_id its generated ID will be used.
+ mod_unique_id, its generated ID will be used.
The first line logs the forensic ID, the request line and all received
headers, separated by pipe characters (|). A sample line
@@ -72,13 +72,13 @@
The plus character at the beginning indicates that this is first log
line of this request. The second line just contains a minus character and
- the id again:
+ the ID again:
-yQtJf8CoAB4AAFNXBIEAAAAA
- The check_forensic script gets as its argument the name
+
The check_forensic script takes as its argument the name
of the logfile. It looks for those +/- ID pairs
and complains if a request was not completed.
@@ -101,11 +101,11 @@
The ForensicLog directive is used to
- log requests to the server for a forensic analysis. Each log entry
- gets assigned unique id which can be associated with the request
+ log requests to the server for forensic analysis. Each log entry
+ is assigned a unique ID which can be associated with the request
using the normal CustomLog
- directive. mod_log_forensic leaves a note called
- forensic-id which can be added to the transfer log by
+ directive. mod_log_forensic creates a token called
+ forensic-id, which can be added to the transfer log
using the %{forensic-id}n format string.
The argument, which specifies the location to which