From: Erik Abele Date: Sat, 24 Aug 2002 11:20:22 +0000 (+0000) Subject: Fixed a lot of typos and link errors. X-Git-Tag: AGB_BEFORE_AAA_CHANGES~171 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d1aa956a8358984682d4c439db0326938bf30536;p=apache Fixed a lot of typos and link errors. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96516 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index 4e3a0d375c..49370295e0 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -1,8 +1,8 @@ -Log Files - Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Log Files

+ -->Log Files - Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Log Files

In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring. The Apache @@ -10,7 +10,7 @@ capabilities. This document describes how to configure its logging capabilities, and how to understand what the logs contain.

-

Security Warning

+

Security Warning

Anyone who can write to the directory where Apache is @@ -29,7 +29,7 @@

Error Log

-
Related Modules

Related Directives

ErrorLog
LogLevel
+
Related Modules

Related Directives

ErrorLog
LogLevel

The server error log, whose name and location is set by the ErrorLog directive, is the @@ -93,7 +93,7 @@

Access Log

-
Related Modules

mod_log_config
mod_setenvif
Related Directives

CustomLog
LogFormat
SetEnvIf
+
Related Modules

mod_log_config
mod_setenvif
Related Directives

CustomLog
LogFormat
SetEnvIf

The server access log records all requests processed by the server. The location and content of the access log are @@ -116,17 +116,14 @@

Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the - TransferLog directive. The CustomLog - directive now subsumes the functionality of all the older - directives.

+ TransferLog directive. The CustomLog directive now subsumes + the functionality of all the older directives.

The format of the access log is highly configurable. The - format is specified using a - CustomLog that + format is specified using a CustomLog that looks much like a C-style printf(1) format string. Some examples are presented in the next sections. For a complete - list of the possible contents of the format string, see the mod_log_config + list of the possible contents of the format string, see the mod_log_config documentation.

Common Log Format

@@ -152,10 +149,11 @@ control characters "\n" for new-line and "\t" for tab.

-

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 - with a slash.

+

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 with a slash.

The above configuration will write log entries in a format known as the Common Log Format (CLF). This standard format can @@ -318,14 +316,13 @@

Multiple access logs can be created simply by specifying - multiple CustomLog + multiple CustomLog directives in the configuration 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 - to mimic the effects of the ReferLog - and AgentLog directives.

+ information. The last two CustomLog lines show how + to mimic the effects of the ReferLog and AgentLog directives.

LogFormat "%h %l %u %t \"%r\" %>s %b" common
@@ -335,9 +332,8 @@

This example also shows that it is not necessary to define a - nickname with the LogFormat directive. Instead, - the log format can be specified directly in the - CustomLog directive.

+ nickname with the LogFormat directive. Instead, + the log format can be specified directly in the CustomLog directive.

Conditional Logs

@@ -349,9 +345,9 @@ environment variable must be set to indicate that the request meets certain conditions. This is usually accomplished with SetEnvIf. Then the - env= clause of the CustomLog - directive is used to include or exclude requests where the - environment variable is set. Some examples:

+ env= clause of the CustomLog directive is used to + include or exclude requests where the environment variable is + set. Some examples:

# Mark requests from the loop-back interface
@@ -480,7 +476,7 @@ hosts.

If CustomLog - or ErrorLog + or ErrorLog directives are placed inside a <VirtualHost> section, all requests or errors for that virtual host will be @@ -511,16 +507,14 @@

Other Log Files

-
Related Modules

mod_cgi
mod_rewrite
Related Directives

PidFile
RewriteLog
RewriteLogLevel
ScriptLog
ScriptLogLength
ScriptBuffer
+
Related Modules

mod_cgi
mod_rewrite
Related Directives

PidFile
RewriteLog
RewriteLogLevel
ScriptLog
ScriptLogBuffer
ScriptLogLength

PID File

On startup, Apache httpd saves the process id of the parent httpd process to the file logs/httpd.pid. This - filename can be changed with the PidFile - directive. The + filename can be changed with the PidFile directive. The process-id is for use by the administrator in restarting and terminating the daemon by sending signals to the parent process; on Windows, use the -k command line option instead. @@ -535,7 +529,7 @@ 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.

+ More information is available in the mod_cgi documentation.

Rewrite Log

@@ -547,4 +541,4 @@ the rewriting engine transforms requests. The level of detail is controlled by the RewriteLogLevel directive.

-

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file +

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 b0af3594ce..3953251294 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -40,8 +40,8 @@ - ErrorLog - LogLevel + ErrorLog + LogLevel @@ -145,17 +145,17 @@

Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the - TransferLog directive. The CustomLog - directive now subsumes the functionality of all the older - directives.

+ TransferLog directive. The CustomLog directive now subsumes + the functionality of all the older directives.

The format of the access log is highly configurable. The - format is specified using a - CustomLog that + format is specified using a CustomLog that looks much like a C-style printf(1) format string. Some examples are presented in the next sections. For a complete list of the possible contents of the format string, see the mod_log_config + href="mod/mod_log_config.html#formats">mod_log_config documentation.

@@ -181,11 +181,11 @@ control characters "\n" for new-line and "\t" for tab.

-

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 - with a slash.

+

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 with a slash.

The above configuration will write log entries in a format known as the Common Log Format (CLF). This standard format can @@ -205,7 +205,7 @@

This is the IP address of the client (remote host) which made the request to the server. If HostnameLookups is + module="core">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 @@ -228,7 +228,7 @@ almost never be used except on tightly controlled internal networks. Apache httpd will not even attempt to determine this information unless IdentityCheck is set + module="core">IdentityCheck is set to On.
frank (%u)
@@ -352,15 +352,15 @@ Multiple Access Logs

Multiple access logs can be created simply by specifying - multiple CustomLog + multiple CustomLog directives in the configuration 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 - to mimic the effects of the ReferLog - and AgentLog directives.

+ module="mod_log_config">CustomLog lines show how + to mimic the effects of the ReferLog and AgentLog directives.

LogFormat "%h %l %u %t \"%r\" %>s %b" common
@@ -370,9 +370,10 @@

This example also shows that it is not necessary to define a - nickname with the LogFormat directive. Instead, - the log format can be specified directly in the - CustomLog directive.

+ nickname with the LogFormat directive. Instead, + the log format can be specified directly in the CustomLog directive.

@@ -385,9 +386,10 @@ environment variable must be set to indicate that the request meets certain conditions. This is usually accomplished with SetEnvIf. Then the - env= clause of the CustomLog - directive is used to include or exclude requests where the - environment variable is set. Some examples:

+ env= clause of the CustomLog directive is used to + include or exclude requests where the environment variable is + set. Some examples:

# Mark requests from the loop-back interface
@@ -526,7 +528,7 @@ hosts.

If CustomLog - or ErrorLog + or ErrorLog directives are placed inside a VirtualHost section, all requests or errors for that virtual host will be @@ -567,12 +569,12 @@ mod_rewrite - PidFile + PidFile RewriteLog RewriteLogLevel ScriptLog + ScriptLogBuffer ScriptLogLength - ScriptBuffer @@ -581,8 +583,8 @@

On startup, Apache httpd saves the process id of the parent httpd process to the file logs/httpd.pid. This - filename can be changed with the PidFile - directive. The + filename can be changed with the PidFile directive. The process-id is for use by the administrator in restarting and terminating the daemon by sending signals to the parent process; on Windows, use the -k command line option instead. @@ -598,7 +600,7 @@ 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.

+ href="mod/mod_cgi.html">mod_cgi documentation.