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 61f97a145658872df05142661a3e8755208bc88e..1cab8baf5c67a45f89527c97c709dbdf903d746a 100644 (file)
--- 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