From 6282b8f36131de54853bf3d3fd307f02341239a0 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Thu, 30 Nov 2023 09:24:21 +0100 Subject: [PATCH] DOC: config: fix mention of request slot in http-response capture It's response slot, not request slot. --- doc/configuration.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index e44f7bc88..e5754a644 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -8303,12 +8303,12 @@ http-response cache-store [ { if | unless } ] http-response capture id [ { if | unless } ] This captures sample expression from the response buffer, and - converts it to a string. The resulting string is stored into the next request - "capture" slot, so it will possibly appear next to some captured HTTP - headers. It will then automatically appear in the logs, and it will be + converts it to a string. The resulting string is stored into the next + response "capture" slot, so it will possibly appear next to some captured + 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 - anything. Please check section 7.3 (Fetching samples) and - "capture response header" for more information. + anything. Please check section 7.3 (Fetching samples) and "capture response + header" for more information. 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.