%% <i>HTTP-status</i> <i>CGI-script-filename</i>
</pre>
-If the error is the that CGI script cannot be run, the log file will
+If the error is that CGI script cannot be run, the log file will
contain
an extra two lines:
<i>error-message</i>
</pre>
-Alternatively, if the error is the result of the script returning the
+Alternatively, if the error is the result of the script returning
incorrect header information (often due to a bug in the script), the
following information is logged:
<b>Status:</b> mod_cgi
<p>
-The size of any PUR or POST entity body that is logged to the file is
+The size of any PUT or POST entity body that is logged to the file is
limited, to prevent the log file growing too big too quickly if large
bodies are being received. By default, up to 1024 bytes are logged,
but this can be changed with this directive.
to create a log file, <code>LogFormat</code> to set a custom format,
and <code>CustomLog</code> to define a log file and format in one go.
The <code>TransferLog</code> and <code>CustomLog</code> directives can
-be use multiple times in each server to cause each request to be
+be used multiple times in each server to cause each request to be
logged to multiple files.
<P>
<ul>
<li>This module is based on mod_log_config distributed with
previous Apache releases, now updated to handle multiple logs.
-There is now no need to re-configure Apache to get use
-configuration log formats.
+There is now no need to re-configure Apache to use configuration log
+formats.
<li>The module also implements the <code>CookieLog</code> directive,
used to log user-tracking information created by <a
<h2>Directives</h2>
<ul>
-<li><a href="#cookieenable">CookieTracking</a>
<li><a href="#cookieexpires">CookieExpires</a>
+<li><a href="#cookietracking">CookieTracking</a>
</ul>
<hr>
+<a name="cookieexpires"><h2>CookieExpires</h2></A>
+<strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br>
+<strong>Context:</strong> server config, virtual host<br>
+<strong>Status:</strong> optional<br>
+<strong>Module:</strong> mod_usertrack<p>
+
+When used, this directive sets an expiry time on the cookie generated
+by the usertrack module. The <i>expiry-period</i> can be given either
+as a number of seconds, or in the format such as "2 weeks 3 days 7
+hours". Valid denominations are: years, months, weeks, hours, minutes
+and seconds.
+
+<p>If this directive is not used, cookies last only for the current
+browser session.</p>
+
<a name="cookieexpires"><h2>CookieTracking</h2></A>
<strong>Syntax:</strong> CookieTracking <em>on | off</em><br>
<strong>Context:</strong> server config, virtual host, directory,
on a per-server or per-directory basis. By default, compiling
mod_usertrack will not activate cookies.
-<a name="cookieexpires"><h2>CookieExpires</h2></A>
-<strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br>
-<strong>Context:</strong> server config, virtual host<br>
-<strong>Status:</strong> optional<br>
-<strong>Module:</strong> mod_usertrack<p>
-
-When used, this directive sets an expiry time on the cookie generated
-by the usertrack module. The <i>expiry-period</i> can be given either
-as a number of seconds, or in the format such as "2 weeks 3 days 7
-hours". Valid denominations are: years, months, weeks, hours, minutes
-and seconds.
-
<!--#include virtual="footer.html" -->
</BODY>