You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2004/03/22 23:06:56 UTC

cvs commit: httpd-2.0/docs/manual/mod mod_log_config.html.en mod_log_config.xml

slive       2004/03/22 14:06:56

  Modified:    docs/manual/mod mod_log_config.html.en mod_log_config.xml
  Log:
  Document the ability to look at original of final subrequest.
  
  I'd appreciate a review from someone more familiar with
  mod_log_config!
  
  PR: 27319
  
  Revision  Changes    Path
  1.41      +11 -0     httpd-2.0/docs/manual/mod/mod_log_config.html.en
  
  Index: mod_log_config.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_log_config.html.en,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -d -b -u -r1.40 -r1.41
  --- mod_log_config.html.en	21 Feb 2004 00:31:36 -0000	1.40
  +++ mod_log_config.html.en	22 Mar 2004 22:06:55 -0000	1.41
  @@ -187,6 +187,17 @@
       "%!200,304,302{Referer}i" logs <code>Referer:</code> on all requests
       which did <em>not</em> return some sort of normal status.</p>
   
  +    <p>The modifiers "&lt;" and "&gt;" can be used for requests that
  +    have been internally redirected to choose whether the original or
  +    final (respectively) request should be consulted.  By default, the
  +    <code>%</code> directives <code>%s, %U, %T, %D,</code> and
  +    <code>%r</code> look at the original request while all others look
  +    at the final request.  So for example, <code>%&gt;s</code> can be
  +    used to record the final status of the request and
  +    <code>%&lt;u</code> can be used to record the original
  +    authenticated user on a request that is internally redirect to an
  +    unauthenticated resource.</p>
  +
       <p>Note that in httpd 2.0 versions prior to 2.0.46, no escaping was performed
       on the strings from <code>%...r</code>, <code>%...i</code> and
       <code>%...o</code>. This was mainly to comply with the requirements of
  
  
  
  1.27      +11 -0     httpd-2.0/docs/manual/mod/mod_log_config.xml
  
  Index: mod_log_config.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_log_config.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -d -b -u -r1.26 -r1.27
  --- mod_log_config.xml	9 Feb 2004 20:16:07 -0000	1.26
  +++ mod_log_config.xml	22 Mar 2004 22:06:55 -0000	1.27
  @@ -209,6 +209,17 @@
       "%!200,304,302{Referer}i" logs <code>Referer:</code> on all requests
       which did <em>not</em> return some sort of normal status.</p>
   
  +    <p>The modifiers "&lt;" and "&gt;" can be used for requests that
  +    have been internally redirected to choose whether the original or
  +    final (respectively) request should be consulted.  By default, the
  +    <code>%</code> directives <code>%s, %U, %T, %D,</code> and
  +    <code>%r</code> look at the original request while all others look
  +    at the final request.  So for example, <code>%&gt;s</code> can be
  +    used to record the final status of the request and
  +    <code>%&lt;u</code> can be used to record the original
  +    authenticated user on a request that is internally redirect to an
  +    unauthenticated resource.</p>
  +
       <p>Note that in httpd 2.0 versions prior to 2.0.46, no escaping was performed
       on the strings from <code>%...r</code>, <code>%...i</code> and
       <code>%...o</code>. This was mainly to comply with the requirements of