httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cove...@apache.org
Subject svn commit: r826006 - in /httpd/httpd/branches/2.2.x/docs/manual/mod: mod_headers.html.en mod_headers.xml
Date Fri, 16 Oct 2009 17:04:47 GMT
Author: covener
Date: Fri Oct 16 17:04:46 2009
New Revision: 826006

URL: http://svn.apache.org/viewvc?rev=826006&view=rev
Log:
be clear that onsuccess is the default, reword explanation of when "always" helps.


Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.html.en
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.html.en?rev=826006&r1=826005&r2=826006&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.html.en Fri Oct 16 17:04:46 2009
@@ -214,12 +214,13 @@
     and output filters are run, allowing outgoing headers to be
     modified.</p>
 
-    <p>The optional <var>condition</var> can be either <code>onsuccess</code>
-    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>By default, this directive only affects successful responses (responses
+    in the <code>2<var>xx</var></code> range).  The optional <var>condition</var>
+    can be either <code>onsuccess</code> (default) or <code>always</code>
(all
+    status codes, including successful responses).  A value of <code>always</code>
+    may be needed to influence headers set by some internal modules even for
+    successful responses, and is always needed to affect non-<code>2<var>xx</var></code>

+    responses such as redirects or client errors</p>.
 
     <p>The action it performs is determined by the second
     argument. This can be one of the following values:</p>

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml?rev=826006&r1=826005&r2=826006&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml Fri Oct 16 17:04:46 2009
@@ -298,12 +298,13 @@
     and output filters are run, allowing outgoing headers to be
     modified.</p>
 
-    <p>The optional <var>condition</var> can be either <code>onsuccess</code>
-    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>By default, this directive only affects successful responses (responses
+    in the <code>2<var>xx</var></code> range).  The optional <var>condition</var>
+    can be either <code>onsuccess</code> (default) or <code>always</code>
(all
+    status codes, including successful responses).  A value of <code>always</code>
+    may be needed to influence headers set by some internal modules even for
+    successful responses, and is always needed to affect non-<code>2<var>xx</var></code>

+    responses such as redirects or client errors</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