DOC: config: Add documentation about spop mode for backends

The SPOE was refactored. Now backends referenced by a SPOE filter must use
the spop mode to be able to use the spop multiplexer for server connections.
The "spop" mode was added in the list of supported mode for backends.
This commit is contained in:
Christopher Faulet 2024-07-29 17:25:37 +02:00
parent 5541d4995d
commit 33c9562f07

View File

@ -8612,7 +8612,7 @@ maxconn <conns>
See also : "server", global section's "maxconn", "fullconn"
mode { tcp|http|log }
mode { tcp|http|log|spop }
Set the running mode or protocol of the instance
May be used in sections : defaults | frontend | listen | backend
yes | yes | yes | yes
@ -8637,6 +8637,10 @@ mode { tcp|http|log }
the server's address with the "udp@" prefix. Common backend and
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
necessary, for backends referenced by SPOE engines.
When doing content switching, it is mandatory that the frontend and the
backend are in the same mode (generally HTTP), otherwise the configuration
will be refused.