RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2025-01-01 01:32:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

DOC: config: fix mention of request slot in http-response capture

Browse Source 
It's response slot, not request slot.
This commit is contained in:
Willy Tarreau 2023-11-30 09:24:21 +01:00
parent 2b6c72abd2
commit 6282b8f361
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/configuration.txt
View File

@ -8303,12 +8303,12 @@ http-response cache-store <name> [ { if | unless } <condition> ]
http-response capture <sample> id <id> [ { if | unless } <condition> ] http-response capture <sample> id <id> [ { if | unless } <condition> ]
This captures sample expression <sample> from the response buffer, and This captures sample expression <sample> from the response buffer, and
converts it to a string. The resulting string is stored into the next request converts it to a string. The resulting string is stored into the next
"capture" slot, so it will possibly appear next to some captured HTTP response "capture" slot, so it will possibly appear next to some captured
headers. It will then automatically appear in the logs, and it will be HTTP headers. It will then automatically appear in the logs, and it will be
possible to extract it using sample fetch rules to feed it into headers or possible to extract it using sample fetch rules to feed it into headers or
anything. Please check section 7.3 (Fetching samples) and anything. Please check section 7.3 (Fetching samples) and "capture response
"capture response header" for more information. header" for more information.
The keyword "id" is the id of the capture slot which is used for storing the The keyword "id" is the id of the capture slot which is used for storing the
string. The capture slot must be defined in an associated frontend. string. The capture slot must be defined in an associated frontend.