From e16dcab92f5b9873b95f17d5aac39894cd498a9a Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Fri, 5 Dec 2025 15:33:02 +0100 Subject: [PATCH] DOC: config: Fix description of the spop mode It was mentionned that the spop mode turned the backend into a "log" backend. It is obviously wrong. It turns the backend into a spop backend. This patch should be backported as far as 3.1. --- doc/configuration.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 98459c440..61f97a145 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -9138,7 +9138,7 @@ mode { tcp|http|log|spop } server features are supported, but not TCP or HTTP specific ones. spop When used in a backend section, it will turn the backend into a - log backend. This mode is mandatory and automatically set, if + spop backend. This mode is mandatory and automatically set, if necessary, for backends referenced by SPOE engines. When doing content switching, it is mandatory that the frontend and the