From 5b149f457fe85e3a7263aff2736eb36e7b6e4055 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Wed, 31 Jul 2002 20:54:22 +0000 Subject: [PATCH] Correct a couple errors in the xml markup. Submitted by: Hiroaki KAWAI git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96266 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/logs.html.en | 44 +++++++++++++--------------------------- docs/manual/logs.xml | 41 +++++++++++++++++++------------------ 2 files changed, 35 insertions(+), 50 deletions(-) diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index a0f71fcc1c..4e3a0d375c 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -97,11 +97,9 @@

The server access log records all requests processed by the server. The location and content of the access log are - controlled by the - CustomLog directive. The - LogFormat directive can be used to simplify the selection of + controlled by the CustomLog + directive. The LogFormat + directive can be used to simplify the selection of the contents of the logs. This section describes how to configure the server to record information in the access log.

@@ -156,9 +154,7 @@

The CustomLog directive sets up a new log file using the defined nickname. The filename for the - access log is relative to the - ServerRoot unless it begins + access log is relative to the ServerRoot unless it begins with a slash.

The above configuration will write log entries in a format @@ -178,9 +174,7 @@

127.0.0.1 (%h)
This is the IP address of the client (remote host) which - made the request to the server. If - HostnameLookups is + made the request to the server. If HostnameLookups is set to On, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can @@ -201,9 +195,7 @@ machine. This information is highly unreliable and should almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine - this information unless - IdentityCheck is set + this information unless IdentityCheck is set to On.
frank (%u)
@@ -331,9 +323,7 @@ file. For example, the following directives will create three access logs. The first contains the basic CLF information, while the second and third contain referer and browser - information. The last two - CustomLog lines show how + information. The last two CustomLog lines show how to mimic the effects of the ReferLog and AgentLog directives.

@@ -483,7 +473,7 @@ hosts, there are several options for dealing with log files. First, it is possible to use logs exactly as in a single-host server. Simply by placing the logging directives - outside the <VirtualHost> sections in the + outside the <VirtualHost> sections in the main server context, it is possible to log all requests in the same access log and error log. This technique does not allow for easy collection of statistics on individual virtual @@ -491,9 +481,8 @@

If CustomLog or ErrorLog - directives are placed inside a - <VirtualHost> + directives are placed inside a + <VirtualHost> section, all requests or errors for that virtual host will be logged only to the specified file. Any virtual host which does not have logging directives will still have its requests sent @@ -542,9 +531,8 @@

Script Log

-

In order to aid in debugging, the - ScriptLog directive +

In order to aid in debugging, the + ScriptLog directive allows you to record the input to and output from CGI scripts. This should only be used in testing - not for live servers. More information is available in the mod_cgi documentation.

@@ -554,13 +542,9 @@

When using the powerful and complex features of mod_rewrite, it is almost - always necessary to use the - RewriteLog to help + always necessary to use the RewriteLog to help in debugging. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail - is controlled by the - RewriteLogLevel directive.

+ is controlled by the RewriteLogLevel directive.

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index ce378c09a0..b0af3594ce 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -124,9 +124,9 @@

The server access log records all requests processed by the server. The location and content of the access log are - controlled by the - CustomLog directive. The - LogFormat directive can be used to simplify the selection of + controlled by the CustomLog + directive. The LogFormat + directive can be used to simplify the selection of the contents of the logs. This section describes how to configure the server to record information in the access log.

@@ -183,8 +183,8 @@

The CustomLog directive sets up a new log file using the defined nickname. The filename for the - access log is relative to the - ServerRoot unless it begins + access log is relative to the ServerRoot unless it begins with a slash.

The above configuration will write log entries in a format @@ -204,8 +204,8 @@

127.0.0.1 (%h)
This is the IP address of the client (remote host) which - made the request to the server. If - HostnameLookups is + made the request to the server. If HostnameLookups is set to On, then the server will try to determine the hostname and log it in place of the IP address. However, this configuration is not recommended since it can @@ -227,8 +227,8 @@ machine. This information is highly unreliable and should almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine - this information unless - IdentityCheck is set + this information unless IdentityCheck is set to On.
frank (%u)
@@ -357,8 +357,8 @@ file. For example, the following directives will create three access logs. The first contains the basic CLF information, while the second and third contain referer and browser - information. The last two - CustomLog lines show how + information. The last two CustomLog lines show how to mimic the effects of the ReferLog and AgentLog directives.

@@ -518,7 +518,8 @@ hosts, there are several options for dealing with log files. First, it is possible to use logs exactly as in a single-host server. Simply by placing the logging directives - outside the <VirtualHost> sections in the + outside the VirtualHost sections in the main server context, it is possible to log all requests in the same access log and error log. This technique does not allow for easy collection of statistics on individual virtual @@ -526,8 +527,8 @@

If CustomLog or ErrorLog - directives are placed inside a - <VirtualHost> + directives are placed inside a + VirtualHost section, all requests or errors for that virtual host will be logged only to the specified file. Any virtual host which does not have logging directives will still have its requests sent @@ -592,8 +593,8 @@

Script Log -

In order to aid in debugging, the - ScriptLog directive +

In order to aid in debugging, the + ScriptLog directive allows you to record the input to and output from CGI scripts. This should only be used in testing - not for live servers. More information is available in the When using the powerful and complex features of mod_rewrite, it is almost - always necessary to use the - RewriteLog to help + always necessary to use the RewriteLog to help in debugging. This log file produces a detailed analysis of how the rewriting engine transforms requests. The level of detail - is controlled by the - RewriteLogLevel directive.

+ is controlled by the RewriteLogLevel directive.

-- 2.50.1