funkman 2003/07/24 05:52:55
Modified: webapps/docs/config valve.xml
Log:
Update for AccessLogValve
Revision Changes Path
1.4 +41 -0 jakarta-tomcat-catalina/webapps/docs/config/valve.xml
Index: valve.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/valve.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- valve.xml 15 Jan 2003 03:40:44 -0000 1.3
+++ valve.xml 24 Jul 2003 12:52:55 -0000 1.4
@@ -99,6 +99,32 @@
use a zero-length string.</p>
</attribute>
+ <attribute name="rotatable" required="false">
+ <p>Deafult true. Flag to determine if log rotation should occur.
+ If set to false, then this file is never rotated and
+ <tt>fileDateFormat</tt> is ignored. Use with caution!
+ </p>
+ </attribute>
+
+ <attribute name="condition" required="false">
+ <p>Turns on conditional logging. If set, requests will be
+ logged only if <tt>ServletRequest.getAttribute()</tt> is
+ null. For example, if this value is set to
+ <tt>junk</tt>, then a particular request will only be logged
+ if <tt>ServletRequest.getAttribute("junk") == null</tt>.
+ The use of Filters is an easy way to set/unset the attribute
+ in the ServletRequest on many different requests.
+ </p>
+ </attribute>
+
+ <attribute name="fileDateFormat" required="false">
+ <p>Allows a customized date format in the access log file name.
+ The date format also decides how often the file is rotated.
+ If you wish to rotate every hour, then set this value
+ to: <tt>yyyy-MM-dd.HH</tt>
+ </p>
+ </attribute>
+
</attributes>
<p>Values for the <code>pattern</code> attribute are made up of literal
@@ -126,7 +152,22 @@
<li><b>%u</b> - Remote user that was authenticated (if any), else '-'</li>
<li><b>%U</b> - Requested URL path</li>
<li><b>%v</b> - Local server name</li>
+ <li><b>%D</b> - Time taken to process the request, in millis</li>
+ <li><b>%T</b> - Time taken to process the request, in seconds</li>
</ul>
+
+ <p>
+ There is also support to write information from the cookie, incoming
+ header, the Session or something else in the ServletRequest.
+ It is modeled after the apache syntax:
+ <ul>
+ <li><b><code>%{xxx}i</code></b> for incoming headers</li>
+ <li><b><code>%{xxx}c</code></b> for a specific cookie</li>
+ <li><b><code>%{xxx}r</code></b> xxx is an attribute in the ServletRequest</li>
+ <li><b><code>%{xxx}s</code></b> xxx is an attribute in the HttpSession</li>
+ </ul>
+ </p>
+
<p>The shorthand pattern name <code>common</code> (which is also the
default) corresponds to <strong>%h %l %u %t "%r" %s %b"</strong>.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
