From 4bf5f434c675d62c1beffb4a4ffbb924d2a1960a Mon Sep 17 00:00:00 2001 From: "Jason S. Lingohr" Date: Sun, 22 Jun 2003 15:58:05 +0000 Subject: [PATCH] Removed superfluous whitespace. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@100330 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/filter.xml | 2 +- docs/manual/handler.xml | 8 ++-- docs/manual/logs.xml | 84 ++++++++++++++++++++--------------------- docs/manual/suexec.xml | 2 +- 4 files changed, 48 insertions(+), 48 deletions(-) diff --git a/docs/manual/filter.xml b/docs/manual/filter.xml index df7d1bc7f9..060d6c450c 100644 --- a/docs/manual/filter.xml +++ b/docs/manual/filter.xml @@ -29,7 +29,7 @@ SetOutputFilter - +

A filter is a process that is applied to data that is sent or received by the server. Data sent by clients to the server is processed by input filters while data sent diff --git a/docs/manual/handler.xml b/docs/manual/handler.xml index 98b5d1d47f..3f38cb9d6c 100644 --- a/docs/manual/handler.xml +++ b/docs/manual/handler.xml @@ -30,7 +30,7 @@ SetHandler - +

A "handler" is an internal Apache representation of the action to be performed when a file is called. Generally, files @@ -86,7 +86,7 @@

The following directives will cause requests for files with the html extension to trigger the launch of the footer.pl CGI script.

- + Action add-footer /cgi-bin/footer.pl
AddHandler add-footer .html @@ -96,7 +96,7 @@ originally requested document (pointed to by the PATH_TRANSLATED environment variable) and making whatever modifications or additions are desired.

- +
Files with HTTP headers @@ -113,7 +113,7 @@ SetHandler send-as-is
</Directory> - +
diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index 2d59374b50..5502743a9f 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -18,7 +18,7 @@
Security Warning - +

Anyone who can write to the directory where Apache is writing a log file can almost certainly gain access to the uid that the server is started as, which is normally root. Do @@ -33,17 +33,17 @@ the log files, so care must be taken in dealing with raw logs.

- +
Error Log - + ErrorLog LogLevel - +

The server error log, whose name and location is set by the ErrorLog directive, is the most important log file. This is the place where Apache httpd @@ -59,18 +59,18 @@ is also possible to have the server send errors to syslog or pipe them to a program.

- +

The format of the error log is relatively free-form and descriptive. But there is certain information that is contained in most error log entries. For example, here is a typical message.

- + [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] client denied by server configuration: /export/home/live/ap/htdocs/test - +

The first item in the log entry is the date and time of the message. The second entry lists the severity of the error being reported. The LogLevel @@ -96,19 +96,19 @@ Since it is possible to customize the access log, you can obtain more information about error conditions using that log file.

- +

During testing, it is often useful to continuously monitor the error log for any problems. On unix systems, you can accomplish this using:

- + tail -f error_log
- +
Access Log - + mod_log_config @@ -120,7 +120,7 @@ SetEnvIf - +

The server access log records all requests processed by the server. The location and content of the access log are controlled by the CustomLog @@ -140,7 +140,7 @@ Open Directory or Yahoo.

- +

Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the @@ -154,10 +154,10 @@ sections. For a complete list of the possible contents of the format string, see the mod_log_config format strings.

- +
Common Log Format - +

A typical configuration for the access log might look as follows.

@@ -165,7 +165,7 @@ LogFormat "%h %l %u %t \"%r\" %>s %b" common
CustomLog logs/access_log common - +

This defines the nickname common and associates it with a particular log format string. The format string consists of percent directives, each of which tell the @@ -183,7 +183,7 @@ 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 be produced by many different web servers and read by many log @@ -194,9 +194,9 @@ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 - +

Each part of this log entry is described below.

- +
127.0.0.1 (%h)
@@ -298,10 +298,10 @@ %B instead.
- +
Combined Log Format - +

Another commonly used format string is called the Combined Log Format. It can be used as follows.

@@ -317,7 +317,7 @@ %{header}i, where header can be any HTTP request header. The access log under this format will look like:

- + 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 @@ -326,7 +326,7 @@

The additional fields are:

- +
"http://www.example.com/start.html" (\"%{Referer}i\")
@@ -344,10 +344,10 @@ itself.
- +
Multiple Access Logs - +

Multiple access logs can be created simply by specifying multiple CustomLog directives in the configuration @@ -372,10 +372,10 @@ the log format can be specified directly in the CustomLog directive.

- +
Conditional Logs - +

There are times when it is convenient to exclude certain entries from the access logs based on characteristics of the client request. This is easily accomplished with the help of

- +
Log Rotation - +

On even a moderately busy server, the quantity of information stored in the log files is very large. The access log file typically grows 1 MB or more per 10,000 requests. It @@ -452,10 +452,10 @@ href="#piped">piped logs as discussed in the next section.

- +
Piped Logs - +

Apache httpd is capable of writing error and access log files through a pipe to another process, rather than directly to a file. This capability dramatically increases the @@ -484,7 +484,7 @@ CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common - +

Notice that quotes are used to enclose the entire command that will be called for the pipe. Although these examples are for the access log, the same technique can be used for the @@ -498,10 +498,10 @@ tool, but they should not be used where a simpler solution like off-line post-processing is available.

- +
Virtual Hosts - +

When running a server with many virtual hosts, there are several options for dealing with log files. First, it is possible to use logs exactly as in a @@ -545,10 +545,10 @@ post-process the access log in order to split it into one file per virtual host.

- +
Other Log Files - + mod_cgi @@ -563,10 +563,10 @@ 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 Stopping and Restarting page.

- +
Script Log - +

In order to aid in debugging, the ScriptLog directive allows you to record the input to and output from CGI scripts. @@ -588,10 +588,10 @@ More information is available in the mod_cgi documentation.

- +
Rewrite Log - +

When using the powerful and complex features of mod_rewrite, it is almost always necessary to use the Is the target user NOT superuser? - +

Presently, suEXEC does not allow 'root' to execute -- 2.50.1