mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-12-16 15:11:01 +01:00
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.
This commit is contained in:
parent
e16dcab92f
commit
2fa3b4c3a3
@ -9138,8 +9138,10 @@ mode { tcp|http|log|spop }
|
|||||||
server features are supported, but not TCP or HTTP specific ones.
|
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 When used in a backend section, it will turn the backend into a
|
||||||
spop backend. This mode is mandatory and automatically set, if
|
spop backend. This mode is mandatory if the backend contains
|
||||||
necessary, for backends referenced by SPOE engines.
|
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
|
When doing content switching, it is mandatory that the frontend and the
|
||||||
backend are in the same mode (generally HTTP), otherwise the configuration
|
backend are in the same mode (generally HTTP), otherwise the configuration
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user