upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-02-03 20:39:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

DOC: config: Improve spop mode documentation
Some checks are pending
Contrib / build (push) Waiting to run
Details
alpine/musl / gcc (push) Waiting to run
Details
VTest / Generate Build Matrix (push) Waiting to run
Details
VTest / (push) Blocked by required conditions
Details
Windows / Windows, gcc, all features (push) Waiting to run
Details

Browse source 
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.
This commit is contained in:
Christopher Faulet 2025-12-08 15:24:00 +01:00
parent e16dcab92f
commit 2fa3b4c3a3
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/configuration.txt
View file

@ -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