From: Eric Covener Date: Thu, 6 Feb 2020 01:40:21 +0000 (+0000) Subject: more alignment in wording X-Git-Tag: 2.5.0-alpha2-ci-test-only~1680 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f88078d34fbf9e91c06aad0b257ba462334b295f;p=thirdparty%2Fapache%2Fhttpd.git more alignment in wording git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1873677 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_headers.xml b/docs/manual/mod/mod_headers.xml index 4a1b5c6d315..26540c10077 100644 --- a/docs/manual/mod/mod_headers.xml +++ b/docs/manual/mod/mod_headers.xml @@ -358,7 +358,7 @@ available in 2.4.10 and later the same name. When a new value is merged onto an existing header it is separated from the existing header with a comma. This is the HTTP standard way of giving a header multiple values. -

Choosing a condition: If the header was added by this module, you must match the condition +

Choosing a condition: If the existing header to be appended to was added by this module, you must match the condition parameter that was originally used. Otherwise, you must determine by trial and error whether always should be specified because you can't reliably know which internal table the existing value is present in.

@@ -384,9 +384,10 @@ available in 2.4.10 and later in a header value, whereas the edit* form will replace every instance of the search pattern if it appears more than once. -

Choosing a condition: Because you cannot reliably know which internal header table might have a match, - you should repeat your edit/edit* directive with both always and - onsuccess.

+

Choosing a condition: Depending on the origins of the header to be edited, + you may have to repeat your edit/edit* directive with both always and + onsuccess. Alternatively, determine by experimentation + whether a condition of always is necessary.

merge
@@ -398,30 +399,27 @@ available in 2.4.10 and later Values are compared in a case sensitive manner, and after all format specifiers have been processed. Values in double quotes are considered different from otherwise identical unquoted values. -

Choosing a condition: If the header was added by this module, you must match the condition - parameter that was originally used. Otherwise, you must determine by trial - and error whether always should be specified because you can't - reliably know which internal table the existing value is present in.

+

Choosing a condition: If the target header to be merged was added by this module, you must match the condition + parameter that was originally used. Otherwise, you must determine by experimentation + whether a condition of always is necessary.

set
The response header is set, replacing any previous header with this name. The value may be a format string. -

Choosing a condition: If the header was added by this module, you must match the condition - parameter that was originally used. Otherwise, you must determine by trial - and error whether always should be specified because you can't - reliably know which internal table the existing value is present in.

+

Choosing a condition: If the target header to be replaced was added by this module, you must match the condition + parameter that was originally used. Otherwise, you must determine by experimentation + whether a condition always is necessary.

setifempty
The request header is set, but only if there is no previous header with this name. -

Choosing a condition: If the header was added by this module, you must match the condition - parameter that was originally used. Otherwise, you must determine by trial - and error whether always should be specified because you can't - reliably know which internal table the existing value is present in.

+

Choosing a condition: If the target header to conditionally set was added by this module, you must match the condition + parameter that was originally used. Otherwise, you must determine by experimentation + whether a condition of always is necessary.

The Content-Type header is a special use case since there might be @@ -439,9 +437,9 @@ available in 2.4.10 and later
The response header of this name is removed, if it exists. If there are multiple headers of the same name, all will be removed. value must be omitted. -

Choosing a condition: Because you cannot reliably know which internal header table might have a match, - you should repeat your this directive with both always and - onsuccess.

+

Choosing a condition: Repeat this directive with both always and + onsuccess to be certain the header is unset, or determine by experimentation + whether a condition of always is necessary..

note
@@ -450,10 +448,9 @@ available in 2.4.10 and later if a header sent by a CGI or proxied resource is configured to be unset but should also be logged.
Available in 2.4.7 and later. -

Choosing a condition: If the header was added by this module, you must match the condition - parameter that was originally used. Otherwise, you must determine by trial - and error whether always should be specified because you can't - reliably know which internal table the existing value is present in.

+

Choosing a condition: If the target header was added by this module, you must match the condition + parameter that was originally used. Otherwise, you must determine by experimentation + whether a condition of always is necessary..