From: Eric Covener
The optional condition can be either onsuccess
- or always
. It determines, which internal header table should be
- operated on. onsuccess
stands for 2xx
- status codes and always
for all status codes (including
- 2xx
). Especially if you want to unset headers
- set by certain modules, you should try out, which table is affected.
By default, this directive only affects successful responses (responses
+ in the 2xx
range). The optional condition
+ can be either onsuccess
(default) or always
(all
+ status codes, including successful responses). A value of always
+ may be needed to influence headers set by some internal modules even for
+ successful responses, and is always needed to affect non-2xx
+ responses such as redirects or client errors
The action it performs is determined by the second argument. This can be one of the following values:
diff --git a/docs/manual/mod/mod_headers.xml b/docs/manual/mod/mod_headers.xml index 8fd54a4bda..4ba00c140f 100644 --- a/docs/manual/mod/mod_headers.xml +++ b/docs/manual/mod/mod_headers.xml @@ -302,12 +302,13 @@ headers and output filters are run, allowing outgoing headers to be modified. -The optional condition can be either onsuccess
- or always
. It determines, which internal header table should be
- operated on. onsuccess
stands for 2xx
- status codes and always
for all status codes (including
- 2xx
). Especially if you want to unset headers
- set by certain modules, you should try out, which table is affected.
By default, this directive only affects successful responses (responses
+ in the 2xx
range). The optional condition
+ can be either onsuccess
(default) or always
(all
+ status codes, including successful responses). A value of always
+ may be needed to influence headers set by some internal modules even for
+ successful responses, and is always needed to affect non-2xx
+ responses such as redirects or client errors
The action it performs is determined by the second argument. This can be one of the following values: