From: Christopher Faulet <cfaulet@haproxy.com>
Date: Mon, 8 Dec 2025 14:24:00 +0000 (+0100)
Subject: DOC: config: Improve spop mode documentation
X-Git-Tag: v3.4-dev1~15
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2fa3b4c3a350f6ba57d89bef73f66e3e0afa8049;p=thirdparty%2Fhaproxy.git

DOC: config: Improve spop mode documentation

The spop mode description was a bit confusing. So let's improve it.

Thanks to @NickMRamirez.

This patch shoud fix issue #3206. It could be backported as far as 3.1.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 61f97a145..1cab8baf5 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -9138,8 +9138,10 @@ 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
-              spop backend. This mode is mandatory and automatically set, if
-              necessary, for backends referenced by SPOE engines.
+              spop backend. This mode is mandatory if the backend contains
+              SPOA servers, but when mode is tcp, it will automatically be
+              converted to mode spop if such servers are detected.
+
 
   When doing content switching, it is mandatory that the frontend and the
   backend are in the same mode (generally HTTP), otherwise the configuration