mod_log_config.xml revision db479b48bd4d75423ed4a45e15b75089d1a8ad72
c3fcea07965f59723831e23da647a77518285b8eslive<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
e942c741056732f50da2074b36fe59805d370650slive<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>
5f5d1b4cc970b7f06ff8ef6526128e9a27303d88nd<!-- $LastChangedRevision$ -->
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding Licensed to the Apache Software Foundation (ASF) under one or more
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding contributor license agreements. See the NOTICE file distributed with
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding this work for additional information regarding copyright ownership.
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding The ASF licenses this file to You under the Apache License, Version 2.0
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding (the "License"); you may not use this file except in compliance with
db479b48bd4d75423ed4a45e15b75089d1a8ad72fielding the License. You may obtain a copy of the License at
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd Unless required by applicable law or agreed to in writing, software
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd distributed under the License is distributed on an "AS IS" BASIS,
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd See the License for the specific language governing permissions and
d5d794fc2f4cc9ca6d6da17cfa2cdcd8d244bacdnd limitations under the License.
c3fcea07965f59723831e23da647a77518285b8eslive<description>Logging of the requests made to the server</description>
6c822625991844de5475569ff656a69965aa6affrbowen <p>This module provides for flexible logging of client
6c822625991844de5475569ff656a69965aa6affrbowen requests. Logs are written in a customizable format, and may be
6c822625991844de5475569ff656a69965aa6affrbowen written directly to a file, or to an external program.
6c822625991844de5475569ff656a69965aa6affrbowen Conditional logging is provided so that individual requests may
6c822625991844de5475569ff656a69965aa6affrbowen be included or excluded from the logs based on characteristics
6c822625991844de5475569ff656a69965aa6affrbowen of the request.</p>
6c822625991844de5475569ff656a69965aa6affrbowen <p>Three directives are provided by this module:
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive module="mod_log_config">TransferLog</directive> to create
10542e490a1b0abf5c02e022f29ea2074ca4d435nd a log file, <directive module="mod_log_config">LogFormat</directive>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd to set a custom format, and <directive module="mod_log_config"
10542e490a1b0abf5c02e022f29ea2074ca4d435nd >CustomLog</directive> to define a log file and format in one
10542e490a1b0abf5c02e022f29ea2074ca4d435nd step. The <directive>TransferLog</directive> and <directive
10542e490a1b0abf5c02e022f29ea2074ca4d435nd >CustomLog</directive> directives can be used multiple times in each
10542e490a1b0abf5c02e022f29ea2074ca4d435nd server to cause each request to be logged to multiple files.</p>
c3fcea07965f59723831e23da647a77518285b8eslive<seealso><a href="/logs.html">Apache Log Files</a></seealso>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <p>The format argument to the <directive module="mod_log_config"
10542e490a1b0abf5c02e022f29ea2074ca4d435nd >LogFormat</directive> and <directive module="mod_log_config"
10542e490a1b0abf5c02e022f29ea2074ca4d435nd >CustomLog</directive> directives is a string. This string is
70d5ff773604d8c7625050947c3a9a764b31dd58pepper used to log each request to the log file. It can contain literal
70d5ff773604d8c7625050947c3a9a764b31dd58pepper characters copied into the log files and the C-style control
6c822625991844de5475569ff656a69965aa6affrbowen characters "\n" and "\t" to represent new-lines and tabs.
6c822625991844de5475569ff656a69965aa6affrbowen Literal quotes and back-slashes should be escaped with
6c822625991844de5475569ff656a69965aa6affrbowen back-slashes.</p>
6c822625991844de5475569ff656a69965aa6affrbowen <p>The characteristics of the request itself are logged by
10542e490a1b0abf5c02e022f29ea2074ca4d435nd placing "<code>%</code>" directives in the format string, which are
10542e490a1b0abf5c02e022f29ea2074ca4d435nd replaced in the log file by the values as follows:</p>
3209c0009829fcf63b6213fb9c43d534f7906006slive <columnspec><column width=".2"/><column width=".8"/></columnspec>
fbf7d2f9b0829a9064d541b1ff65d0ecf56b9364jorton <td>Size of response in bytes, excluding HTTP headers.</td></tr>
fbf7d2f9b0829a9064d541b1ff65d0ecf56b9364jorton <td>Size of response in bytes, excluding HTTP headers. In CLF format, <em>i.e.</em>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd a '<code>-</code>' rather than a 0 when no bytes are sent.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The contents of cookie <var>Foobar</var> in the request sent
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The time taken to serve the request, in microseconds.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The contents of the environment variable
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The contents of <code><var>Foobar</var>:</code> header line(s)
77b840c850ef60fd6a119f3a7e907412d78b77d5nd <td>Remote logname (from identd, if supplied). This will return a
77b840c850ef60fd6a119f3a7e907412d78b77d5nd dash unless <module>mod_ident</module> is present and <directive
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The contents of <code><var>Foobar</var>:</code> header line(s)
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The canonical port of the server serving the request</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The process ID of the child that serviced the request.</td></tr>
349eb1baf455be0d2b9009dab951e5b1ba13dd2ftrawick <td>The process ID or thread id of the child that serviced the
6ecde05c829c9d0aa24b2b1c18b40c8739997571trawick request. Valid formats are <code>pid</code>, <code>tid</code>,
6ecde05c829c9d0aa24b2b1c18b40c8739997571trawick and <code>hextid</code>. <code>hextid</code> requires APR 1.2.0 or
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The query string (prepended with a <code>?</code> if a query
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>Status. For requests that got internally redirected, this is
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive the status of the *original* request --- <code>%>s</code>
497098c4742b6d074b19c2aebb8d6715cae0a1aeslive <td>Time the request was received (standard english
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The time, in the form given by format, which should be in
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <code>strftime(3)</code> format. (potentially localized)</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The time taken to serve the request, in seconds.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>Remote user (from auth; may be bogus if return status
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The URL path requested, not including any query string.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The canonical <directive module="core">ServerName</directive>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>The server name according to the <directive module="core"
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>Connection status when response is completed:
3209c0009829fcf63b6213fb9c43d534f7906006slive <columnspec><column width=".2"/><column width=".6"/></columnspec>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>connection aborted before the response completed.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>connection may be kept alive after the response is
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>connection will be closed after the response is
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <p>(This directive was <code>%c</code> in late versions of Apache
10542e490a1b0abf5c02e022f29ea2074ca4d435nd 1.3, but this conflicted with the historical ssl
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>%{<var>var</var>}c</code> syntax.)</p></td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>Bytes received, including request and headers, cannot be zero.
10542e490a1b0abf5c02e022f29ea2074ca4d435nd You need to enable <module>mod_logio</module> to use this.</td></tr>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <td>Bytes sent, including headers, cannot be zero. You need to
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <p>Particular items can be restricted to print only for
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive responses with specific HTTP status codes by placing a
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive comma-separated list of status codes immediately following the
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive "%". For example, <code>"%400,501{User-agent}i"</code> logs
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>User-agent</code> on 400 errors and 501 errors only. For
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive other status codes, the literal string <code>"-"</code> will be
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive logged. The status code list may be preceded by a
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>"%!200,304,302{Referer}i"</code> logs <code>Referer</code>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive on all requests that do <em>not</em> return one of the three
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive specified codes.</p>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <p>The modifiers "<" and ">" can be used for requests that
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive have been internally redirected to choose whether the original
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive or final (respectively) request should be consulted. By
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive default, the <code>%</code> directives <code>%s, %U, %T,
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive %D,</code> and <code>%r</code> look at the original request
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive while all others look at the final request. So for example,
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>%>s</code> can be used to record the final status of
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive the request and <code>%<u</code> can be used to record the
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive original authenticated user on a request that is internally
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive redirected to an unauthenticated resource.</p>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <p>For security reasons, starting with version 2.0.46,
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive non-printable and other special characters in <code>%r</code>,
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>\x<var>hh</var></code> sequences, where <var>hh</var>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive stands for the hexadecimal representation of the raw
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive byte. Exceptions from this rule are <code>"</code> and
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>\</code>, which are escaped by prepending a backslash, and
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive all whitespace characters, which are written in their C-style
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive notation (<code>\n</code>, <code>\t</code>, etc). In versions
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive prior to 2.0.46, no escaping was performed on these strings so
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive you had to be quite careful when dealing with raw log files.</p>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <code>%B</code> format strings do not represent the number of
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive bytes sent to the client, but simply the size in bytes of the
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive HTTP response (which will differ, for instance, if the
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive connection is aborted, or if SSL is used). The <code>%O</code>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive format provided by <module>mod_logio</module> will log the
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive actual number of bytes sent over the network.</p>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <dd><code>"%v %h %l %u %t \"%r\" %>s %b"</code></dd>
c244470ffb627d4fd092f8bdcc7c1b8e6b7dc70cslive <dd><code>"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<section id="security"><title>Security Considerations</title>
6c822625991844de5475569ff656a69965aa6affrbowen href="/misc/security_tips.html#serverroot">security tips</a>
6c822625991844de5475569ff656a69965aa6affrbowen document for details on why your security could be compromised
6c822625991844de5475569ff656a69965aa6affrbowen if the directory where logfiles are stored is writable by
6c822625991844de5475569ff656a69965aa6affrbowen anyone other than the user that starts the server.</p>
5975f159b503abf6ccd3ff8910fad74e9549801aslive<directivesynopsis>
5975f159b503abf6ccd3ff8910fad74e9549801aslive<description>Buffer log entries in memory before writing to disk</description>
5975f159b503abf6ccd3ff8910fad74e9549801aslive<contextlist><context>server config</context></contextlist>
abe1076e4b4bfbbcbfa26f9cb45ffb985ba2927cnd<compatibility>Available in versions 2.0.41 and later.</compatibility>
5975f159b503abf6ccd3ff8910fad74e9549801aslive <p>The <directive>BufferedLogs</directive> directive causes
5975f159b503abf6ccd3ff8910fad74e9549801aslive <module>mod_log_config</module> to store several log entries in
5975f159b503abf6ccd3ff8910fad74e9549801aslive memory and write them together to disk, rather than writing them
5975f159b503abf6ccd3ff8910fad74e9549801aslive after each request. On some systems, this may result in more
5975f159b503abf6ccd3ff8910fad74e9549801aslive efficient disk access and hence higher performance. It may be
5975f159b503abf6ccd3ff8910fad74e9549801aslive set only once for the entire server; it cannot be configured
5975f159b503abf6ccd3ff8910fad74e9549801aslive per virtual-host.</p>
5975f159b503abf6ccd3ff8910fad74e9549801aslive <note>This directive is experimental and should be used with
5975f159b503abf6ccd3ff8910fad74e9549801aslive caution.</note>
5975f159b503abf6ccd3ff8910fad74e9549801aslive</directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<description>Sets filename for the logging of cookies</description>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<contextlist><context>server config</context><context>virtual host</context>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd</contextlist>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<compatibility>This directive is deprecated.</compatibility>
6c822625991844de5475569ff656a69965aa6affrbowen <p>The <directive>CookieLog</directive> directive sets the
6c822625991844de5475569ff656a69965aa6affrbowen filename for logging of cookies. The filename is relative to the
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive module="core">ServerRoot</directive>. This directive is
199a8ee5984e3708982fab1ba6ebb0a5feaea90cnd included only for compatibility with <code>mod_cookies</code>,
6c822625991844de5475569ff656a69965aa6affrbowen and is deprecated.</p>
6c822625991844de5475569ff656a69965aa6affrbowen</directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<description>Sets filename and format of log file</description>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<contextlist><context>server config</context><context>virtual host</context>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd</contextlist>
6c822625991844de5475569ff656a69965aa6affrbowen <p>The <directive>CustomLog</directive> directive is used to
6c822625991844de5475569ff656a69965aa6affrbowen log requests to the server. A log format is specified, and the
6c822625991844de5475569ff656a69965aa6affrbowen logging can optionally be made conditional on request
6c822625991844de5475569ff656a69965aa6affrbowen characteristics using environment variables.</p>
6c822625991844de5475569ff656a69965aa6affrbowen <p>The first argument, which specifies the location to which
70d5ff773604d8c7625050947c3a9a764b31dd58pepper the logs will be written, can take one of the following two
6c822625991844de5475569ff656a69965aa6affrbowen types of values:</p>
6c822625991844de5475569ff656a69965aa6affrbowen <dd>The pipe character "<code>|</code>", followed by the path
6c822625991844de5475569ff656a69965aa6affrbowen to a program to receive the log information on its standard
70d5ff773604d8c7625050947c3a9a764b31dd58pepper <p>If a program is used, then it will be run as the user who
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd started <program>httpd</program>. This will be root if the server was
a1ef40892ffa2b44fc249423c5b6c42a74a84c68nd started by root; be sure that the program is secure.</p>
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes <p>When entering a file path on non-Unix platforms, care should be taken
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes to make sure that only forward slashed are used even though the platform
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes may allow the use of back slashes. In general it is a good idea to always
2bac697634d965d9d9a921a99a68b2c454c8a95dbnicholes use forward slashes throughout the configuration files.</p>
6c822625991844de5475569ff656a69965aa6affrbowen <p>The second argument specifies what will be written to the
10542e490a1b0abf5c02e022f29ea2074ca4d435nd log file. It can specify either a <var>nickname</var> defined by
10542e490a1b0abf5c02e022f29ea2074ca4d435nd a previous <directive module="mod_log_config">LogFormat</directive>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd directive, or it can be an explicit <var>format</var> string as
10542e490a1b0abf5c02e022f29ea2074ca4d435nd described in the <a href="#formats">log formats</a> section.</p>
6c822625991844de5475569ff656a69965aa6affrbowen <p>For example, the following two sets of directives have
6c822625991844de5475569ff656a69965aa6affrbowen exactly the same effect:</p>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd # CustomLog with format nickname<br />
10542e490a1b0abf5c02e022f29ea2074ca4d435nd LogFormat "%h %l %u %t \"%r\" %>s %b" common<br />
10542e490a1b0abf5c02e022f29ea2074ca4d435nd # CustomLog with explicit format string<br />
10542e490a1b0abf5c02e022f29ea2074ca4d435nd </example>
70d5ff773604d8c7625050947c3a9a764b31dd58pepper <p>The third argument is optional and controls whether or
70d5ff773604d8c7625050947c3a9a764b31dd58pepper not to log a particular request based on the
6c822625991844de5475569ff656a69965aa6affrbowen presence or absence of a particular variable in the server
6c822625991844de5475569ff656a69965aa6affrbowen environment. If the specified <a href="/env.html">environment
6c822625991844de5475569ff656a69965aa6affrbowen variable</a> is set for the request (or is not set, in the case
10542e490a1b0abf5c02e022f29ea2074ca4d435nd of a '<code>env=!<var>name</var></code>' clause), then the
6c822625991844de5475569ff656a69965aa6affrbowen request will be logged.</p>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <p>Environment variables can be set on a per-request
01814afd8daa1fb017fcb956ac01d173763f896eyoshiki example, if you want to record requests for all GIF
01814afd8daa1fb017fcb956ac01d173763f896eyoshiki images on your server in a separate logfile but not in your main
6c822625991844de5475569ff656a69965aa6affrbowen log, you can use:</p>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd SetEnvIf Request_URI \.gif$ gif-image<br />
10542e490a1b0abf5c02e022f29ea2074ca4d435nd CustomLog nongif-requests.log common env=!gif-image
10542e490a1b0abf5c02e022f29ea2074ca4d435nd </example>
de3924e33206c661b865aaa91b025f8814793996rbowen <p>Or, to reproduce the behavior of the old RefererIgnore
de3924e33206c661b865aaa91b025f8814793996rbowen directive, you might use the following:</p>
de3924e33206c661b865aaa91b025f8814793996rbowen SetEnvIf Referer example\.com localreferer<br />
de3924e33206c661b865aaa91b025f8814793996rbowen CustomLog referer.log referer env=!localreferer
6c822625991844de5475569ff656a69965aa6affrbowen</directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<description>Describes a format for use in a log file</description>
7cb7b06acc8700479d4d4080b8c7bc5278f20028slive<default>LogFormat "%h %l %u %t \"%r\" %>s %b"</default>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<contextlist><context>server config</context><context>virtual host</context>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd</contextlist>
6c822625991844de5475569ff656a69965aa6affrbowen <p>This directive specifies the format of the access log
6c822625991844de5475569ff656a69965aa6affrbowen <p>The <directive>LogFormat</directive> directive can take one of two
6c822625991844de5475569ff656a69965aa6affrbowen forms. In the first form, where only one argument is specified,
6c822625991844de5475569ff656a69965aa6affrbowen this directive sets the log format which will be used by logs
6c822625991844de5475569ff656a69965aa6affrbowen specified in subsequent <directive>TransferLog</directive>
6c822625991844de5475569ff656a69965aa6affrbowen directives. The single argument can specify an explicit
70d5ff773604d8c7625050947c3a9a764b31dd58pepper <var>format</var> as discussed in the <a href="#formats">custom log
6c822625991844de5475569ff656a69965aa6affrbowen formats</a> section above. Alternatively, it can use a
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <var>nickname</var> to refer to a log format defined in a
6c822625991844de5475569ff656a69965aa6affrbowen previous <directive>LogFormat</directive> directive as described
6c822625991844de5475569ff656a69965aa6affrbowen <p>The second form of the <directive>LogFormat</directive>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd directive associates an explicit <var>format</var> with a
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <var>nickname</var>. This <var>nickname</var> can then be used in
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive module="mod_log_config">CustomLog</directive> directives
10542e490a1b0abf5c02e022f29ea2074ca4d435nd rather than repeating the entire format string. A
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive>LogFormat</directive> directive that defines a nickname
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <strong>does nothing else</strong> -- that is, it <em>only</em>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd defines the nickname, it doesn't actually apply the format and make
10542e490a1b0abf5c02e022f29ea2074ca4d435nd it the default. Therefore, it will not affect subsequent
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive module="mod_log_config">TransferLog</directive> directives.
10542e490a1b0abf5c02e022f29ea2074ca4d435nd In addition, <directive>LogFormat</directive> cannot use one nickname
70d5ff773604d8c7625050947c3a9a764b31dd58pepper to define another nickname. Note that the nickname should not contain
10542e490a1b0abf5c02e022f29ea2074ca4d435nd LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common
10542e490a1b0abf5c02e022f29ea2074ca4d435nd </example>
6c822625991844de5475569ff656a69965aa6affrbowen</directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen<directivesynopsis>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<syntax>TransferLog <var>file</var>|<var>pipe</var></syntax>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd<contextlist><context>server config</context><context>virtual host</context>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd</contextlist>
6c822625991844de5475569ff656a69965aa6affrbowen <p>This directive has exactly the same arguments and effect as
10542e490a1b0abf5c02e022f29ea2074ca4d435nd the <directive module="mod_log_config">CustomLog</directive>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd directive, with the exception that it does not allow the log format
10542e490a1b0abf5c02e022f29ea2074ca4d435nd to be specified explicitly or for conditional logging of requests.
10542e490a1b0abf5c02e022f29ea2074ca4d435nd Instead, the log format is determined by the most recently specified
10542e490a1b0abf5c02e022f29ea2074ca4d435nd <directive module="mod_log_config">LogFormat</directive> directive
70d5ff773604d8c7625050947c3a9a764b31dd58pepper which does not define a nickname. Common Log Format is used if no
6c822625991844de5475569ff656a69965aa6affrbowen other format has been specified.</p>
10542e490a1b0abf5c02e022f29ea2074ca4d435nd LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""<br />
10542e490a1b0abf5c02e022f29ea2074ca4d435nd </example>
6c822625991844de5475569ff656a69965aa6affrbowen</directivesynopsis>
6c822625991844de5475569ff656a69965aa6affrbowen</modulesynopsis>