slipenkomk/haproxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DOC: config: fix alphabetical ordering of http-after-response rules

Browse Source 
The 'capture' action must be placed after the 'allow' action.

This patch could be backported as far as 2.5.

(cherry picked from commit d9d36b8b6bb4d8180b54b24148292a43b08041ce)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 47192fe67fb71fd27ef4f9c9d3427aa706462051)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
This commit is contained in:
Christopher Faulet 2023-01-05 10:25:30 +01:00
parent d02e1170f8
commit 32616807a9
1 changed files with 5 additions and 5 deletions

10
doc/configuration.txt

@ -5703,17 +5703,17 @@ http-after-response add-header <name> <fmt> [ { if | unless } <condition> ]
value is defined by <fmt>. Please refer to "http-request add-header" for a
complete description.
http-after-response allow [ { if | unless } <condition> ]
This stops the evaluation of the rules and lets the response pass the check.
No further "http-after-response" rules are evaluated for the current section.
http-after-response capture <sample> id <id> [ { if | unless } <condition> ]
This captures sample expression <sample> from the response buffer, and
converts it to a string. Please refer to "http-response capture" for a
complete description.
http-after-response allow [ { if | unless } <condition> ]
This stops the evaluation of the rules and lets the response pass the check.
No further "http-after-response" rules are evaluated for the current section.
http-after-response del-header <name> [ -m <meth> ] [ { if | unless } <condition> ]
This removes all HTTP header fields whose name is specified in <name>. Please