From c9d735fd3f2a132511688e6e35df9b6baeb62119 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Mon, 18 Nov 2024 22:48:23 +0100 Subject: [PATCH] DOC: config: Slightly improve the %Tr documentation Specify -1 can also be reported for %Tr delay when the response is invalid. (cherry picked from commit e9021a4ca1d6a70cb647441aae78ec4d35bb7c1a) Signed-off-by: Christopher Faulet --- doc/configuration.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 26db87e..4ef5550 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -26581,9 +26581,10 @@ Timings events in TCP mode: instance during a POST request, the time already runs, and this can distort apparent response time. For this reason, it's generally wise not to trust too much this field for POST requests initiated from clients behind an - untrusted network. A value of "-1" here means that the last the response - header (empty line) was never seen, most likely because the server timeout - stroke before the server managed to process the request. + untrusted network. A value of "-1" here means that the last response header + (empty line) was never seen, most likely because the server timeout stroke + before the server managed to process the request or because the server + returned an invalid response. This timer is named %Tr as a log-format alias, and res.timer.hdr as a sample fetch. -- 1.7.10.4