From 33c9562f07bb6abb3bec63e78a9cc7cf6ab45226 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Mon, 29 Jul 2024 17:25:37 +0200 Subject: [PATCH] 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. --- doc/configuration.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 62bfff2f0..529061bf2 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -8612,7 +8612,7 @@ maxconn 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.