httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_headers.xml
Date Sat, 12 Jun 2004 14:17:05 GMT
nd          2004/06/12 07:17:05

  Modified:    docs/manual/mod mod_headers.xml
  Log:
  describe the onsuccess and always options better
  
  Revision  Changes    Path
  1.17      +6 -5      httpd-2.0/docs/manual/mod/mod_headers.xml
  
  Index: mod_headers.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_headers.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -u -r1.16 -r1.17
  --- mod_headers.xml	11 Jun 2004 21:57:04 -0000	1.16
  +++ mod_headers.xml	12 Jun 2004 14:17:05 -0000	1.17
  @@ -209,10 +209,11 @@
       modified.</p>
   
       <p>The optional <var>condition</var> can be either <code>onsuccess</code>
  -    or <code>always</code>. It determines, when the specified action should
be
  -    taken. <code>onsuccess</code> stands for <code>2<var>xx</var></code>
status
  -    codes and <code>always</code> for all status codes (including
  -    <code>2<var>xx</var></code>).</p>
  +    or <code>always</code>. It determines, which internal header table should
be
  +    operated on. <code>onsuccess</code> stands for <code>2<var>xx</var></code>
  +    status codes and <code>always</code> for all status codes (including
  +    <code>2<var>xx</var></code>). Especially if you want to unset
headers
  +    set by certain modules, you should try out, which table is affected.</p>
   
       <p>The action it performs is determined by the second
       argument. This can be one of the following values:</p>
  
  
  

Mime
View raw message