From 4387be7a975f65379130aab535e4bddfd88d9f98 Mon Sep 17 00:00:00 2001 From: Benedict Weis Date: Mon, 28 Sep 2026 13:11:35 +0000 Subject: [PATCH 2/3] DOC: spoe: document the "on-frontend-tcp-request-done" event Document the new "on-frontend-tcp-request-done" event in the list of supported events, next to "on-frontend-tcp-request". It describes that the event is triggered on the frontend after "tcp-request content" rules and before "use_backend" switching rules, and the conditions under which request data is available. This is a new feature, no backport needed. Co-authored-by: Alexander Stephan --- doc/SPOE.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/SPOE.txt b/doc/SPOE.txt index 15628fcfb..8e854ca73 100644 --- a/doc/SPOE.txt +++ b/doc/SPOE.txt @@ -1022,6 +1022,19 @@ Here is the list of supported events: This event is only available for SPOE filters declared in a frontend or a listen section. + * on-frontend-tcp-request-done + is triggered after the evaluation of + "tcp-request content" rules on the frontend side, + just before the "use_backend" switching rules. It + allows an agent to influence the backend selection. + This event is only available for SPOE filters + declared in a frontend or a listen section. Note + that, in TCP mode, request data is only guaranteed + to be available if a "tcp-request content" rule + (combined with a "tcp-request inspect-delay") waits + for it; otherwise the event fires as soon as the + connection is established. + * on-backend-tcp-request is triggered just before the evaluation of "tcp-request content" rules on the backend side. This event is skipped for SPOE filters declared -- 2.51.0