<p>The server access log records all requests processed by the
server. The location and content of the access log are
- controlled by the <a href="./mod/mod_log_config.html#
- customlog" class="directive"><code class="directive">
- CustomLog</code></a> directive. The <a href="./mod/mod_log_config.html#
- logformat" class="directive"><code class="directive">
- LogFormat</code></a> directive can be used to simplify the selection of
+ controlled by the <a href="./mod/mod_log_config.html#customlog" class="directive"><code class="directive">CustomLog</code></a>
+ directive. The <a href="./mod/mod_log_config.html#logformat" class="directive"><code class="directive">LogFormat</code></a>
+ 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.</p>
<p>The <code>CustomLog</code> directive sets up a new log file
using the defined <em>nickname</em>. The filename for the
- access log is relative to the <a href="./mod/core.html#
- serverroot" class="directive"><code class="directive">
- ServerRoot</code></a> unless it begins
+ access log is relative to the <a href="./mod/core.html#serverroot" class="directive"><code class="directive">ServerRoot</code></a> unless it begins
with a slash.</p>
<p>The above configuration will write log entries in a format
<dt><code>127.0.0.1</code> (<code>%h</code>)</dt>
<dd>This is the IP address of the client (remote host) which
- made the request to the server. If <a href="./mod/core.html#
- hostnamelookups" class="directive"><code class="directive">
- HostnameLookups</code></a> is
+ made the request to the server. If <a href="./mod/core.html#hostnamelookups" class="directive"><code class="directive">HostnameLookups</code></a> is
set to <code>On</code>, 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
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 <a href="./mod/core.html#
- identitycheck" class="directive"><code class="directive">
- IdentityCheck</code></a> is set
+ this information unless <a href="./mod/core.html#identitycheck" class="directive"><code class="directive">IdentityCheck</code></a> is set
to <code>On</code>.</dd>
<dt><code>frank</code> (<code>%u</code>)</dt>
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 <a href="./mod/core.html#
- customlog" class="directive"><code class="directive">
- CustomLog</code></a> lines show how
+ information. The last two <a href="./mod/core.html#customlog" class="directive"><code class="directive">CustomLog</code></a> lines show how
to mimic the effects of the <a href="./mod/core.html#referlog" class="directive"><code class="directive">ReferLog</code></a>
and <a href="./mod/core.html#agentlog" class="directive"><code class="directive">AgentLog</code></a> directives.</p>
hosts</a>, 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 <code><VirtualHost></code> sections in the
+ outside the <a href="./mod/core.html#virtualhost" class="directive"><code class="directive"><VirtualHost></code></a> 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
<p>If <a href="./mod/mod_log_config.html#customlog" class="directive"><code class="directive">CustomLog</code></a>
or <a href="./mod/mod_log_config.html#errorlog" class="directive"><code class="directive">ErrorLog</code></a>
- directives are placed inside a <a href="./mod/core.html#
- <virtualhost>" class="directive"><code class="directive">
- <VirtualHost></code></a>
+ directives are placed inside a
+ <a href="./mod/core.html#virtualhost" class="directive"><code class="directive"><VirtualHost></code></a>
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
<h3><a name="scriptlog">Script Log</a></h3>
- <p>In order to aid in debugging, the <a href="./mod/mod_cgi.html#
- scriptlog" class="directive"><code class="directive">
- ScriptLog</code></a> directive
+ <p>In order to aid in debugging, the
+ <a href="./mod/mod_cgi.html#scriptlog" class="directive"><code class="directive">ScriptLog</code></a> 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 <a href="mod/mod_cgi.html">mod_cgi documentation</a>.</p>
<p>When using the powerful and complex features of <a href="mod/mod_rewrite.html">mod_rewrite</a>, it is almost
- always necessary to use the <a href="./mod/mod_rewrite.html#
- rewritelog" class="directive"><code class="directive">
- RewriteLog</code></a> to help
+ always necessary to use the <a href="./mod/mod_rewrite.html#rewritelog" class="directive"><code class="directive">RewriteLog</code></a> 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 <a href="./mod/mod_rewrite.html#
- rewriteloglevel" class="directive"><code class="directive">
- RewriteLogLevel</code></a> directive.</p>
+ is controlled by the <a href="./mod/mod_rewrite.html#rewriteloglevel" class="directive"><code class="directive">RewriteLogLevel</code></a> directive.</p>
<hr/></blockquote><h3 align="center">Apache HTTP Server Version 2.0</h3><a href="./"><img src="./images/index.gif" alt="Index"/></a><a href="./"><img src="./images/home.gif" alt="Home"/></a></body></html>
\ No newline at end of file
<p>The server access log records all requests processed by the
server. The location and content of the access log are
- controlled by the <directive module="mod_log_config">
- CustomLog</directive> directive. The <directive module="mod_log_config">
- LogFormat</directive> directive can be used to simplify the selection of
+ controlled by the <directive module="mod_log_config">CustomLog</directive>
+ directive. The <directive module="mod_log_config">LogFormat</directive>
+ 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.</p>
<p>The <code>CustomLog</code> directive sets up a new log file
using the defined <em>nickname</em>. The filename for the
- access log is relative to the <directive module="core">
- ServerRoot</directive> unless it begins
+ access log is relative to the <directive
+ module="core">ServerRoot</directive> unless it begins
with a slash.</p>
<p>The above configuration will write log entries in a format
<dt><code>127.0.0.1</code> (<code>%h</code>)</dt>
<dd>This is the IP address of the client (remote host) which
- made the request to the server. If <directive module="core">
- HostnameLookups</directive> is
+ made the request to the server. If <directive
+ module="core">HostnameLookups</directive> is
set to <code>On</code>, 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
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 <directive module="core">
- IdentityCheck</directive> is set
+ this information unless <directive
+ module="core">IdentityCheck</directive> is set
to <code>On</code>.</dd>
<dt><code>frank</code> (<code>%u</code>)</dt>
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 <directive module="core">
- CustomLog</directive> lines show how
+ information. The last two <directive
+ module="core">CustomLog</directive> lines show how
to mimic the effects of the <directive module="core">ReferLog</directive>
and <directive module="core">AgentLog</directive> directives.</p>
hosts</a>, 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 <code><VirtualHost></code> sections in the
+ outside the <directive module="core"
+ type="section">VirtualHost</directive> 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
<p>If <directive module="mod_log_config">CustomLog</directive>
or <directive module="mod_log_config">ErrorLog</directive>
- directives are placed inside a <directive module="core">
- <VirtualHost></directive>
+ directives are placed inside a
+ <directive module="core" type="section">VirtualHost</directive>
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
<section id="scriptlog">
<title>Script Log</title>
- <p>In order to aid in debugging, the <directive module="mod_cgi">
- ScriptLog</directive> directive
+ <p>In order to aid in debugging, the
+ <directive module="mod_cgi">ScriptLog</directive> 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 <a
<p>When using the powerful and complex features of <a
href="mod/mod_rewrite.html">mod_rewrite</a>, it is almost
- always necessary to use the <directive module="mod_rewrite">
- RewriteLog</directive> to help
+ always necessary to use the <directive
+ module="mod_rewrite">RewriteLog</directive> 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 <directive module="mod_rewrite">
- RewriteLogLevel</directive> directive.</p>
+ is controlled by the <directive
+ module="mod_rewrite">RewriteLogLevel</directive> directive.</p>
</section>
</section>
</manualpage>
projects / apache / commitdiff