From: Erik Abele Date: Fri, 19 Oct 2007 13:30:57 +0000 (+0000) Subject: Transformations. X-Git-Tag: 2.0.62~80 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=070ecbb29d110522034988825e8988a11c0aff65;p=thirdparty%2Fapache%2Fhttpd.git Transformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x@586438 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en index 864ba31ee2d..dba76419d34 100644 --- a/docs/manual/logs.html.en +++ b/docs/manual/logs.html.en @@ -75,8 +75,8 @@ what went wrong and how to fix it.

The error log is usually written to a file (typically - error_log on unix systems and - error.log on Windows and OS/2). On unix systems it + error_log on Unix systems and + error.log on Windows and OS/2). On Unix systems it is also possible to have the server send errors to syslog or pipe them to a program.

@@ -93,11 +93,11 @@

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 + message. The second item lists the severity of the error being reported. The LogLevel directive is used to control the types of errors that are sent to the error log by restricting the severity level. The third - entry gives the IP address of the client that generated the + item gives the IP address of the client that generated the error. Beyond that is the message itself, which in this case indicates that the server has been configured to deny the client access. The server reports the file-system path (as @@ -111,14 +111,14 @@

It is not possible to customize the error log by adding or removing information. However, error log entries dealing with - particular requests have corresponding entries in the access log. For instance, the above example + particular requests have corresponding entries in the access log. For example, the above example entry corresponds to an access log entry with status code 403. 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 + the error log for any problems. On Unix systems, you can accomplish this using:

@@ -224,7 +224,7 @@

The "hyphen" in the output indicates that the requested piece of information is not available. In this case, the information that is not available is the RFC 1413 identity of - the client determined by identd on the client's + the client determined by identd on the clients 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 @@ -240,7 +240,7 @@ code for the request (see below) is 401, then this value should not be trusted because the user is not yet authenticated. If the document is not password protected, - this entry will be "-" just like the previous + this part will be "-" just like the previous one.
[10/Oct/2000:13:55:36 -0700] @@ -293,7 +293,7 @@
2326 (%b)
-
The last entry indicates the size of the object returned +
The last part indicates the size of the object returned to the client, not including the response headers. If no content was returned to the client, this value will be "-". To log "0" for no content, use diff --git a/docs/manual/logs.xml.es b/docs/manual/logs.xml.es index 11272d11cc5..d0e6e014e96 100644 --- a/docs/manual/logs.xml.es +++ b/docs/manual/logs.xml.es @@ -1,7 +1,7 @@ - + + +