From cfb3d8b67a82edf71c7c034fa8adbd6f6f3b921f Mon Sep 17 00:00:00 2001 From: =?utf8?q?Bj=C3=B6rn=20Jacke?= Date: Tue, 6 Oct 2026 22:55:50 +0200 Subject: [PATCH] DOC: config: explain per ACL line limitations Explain that per ACL line only a single acl matching statement is allowed. Should be backported to all supported branches. Acked-by: Lukas Tribus --- doc/configuration.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 8aad178ea..055ee2813 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -21181,7 +21181,13 @@ Their evaluation only returns a match or a mismatch, which is comparable to booleans in many programming languages. Contrary to functions in programming languages, ACLs may be overloaded as many times as needed in order to define additional matching methods for the same name. In this case they will all be -evaluated in their declaration order until one matches. +evaluated in their declaration order until one matches. In other words, +multiple declarations of the same ACL name are logically combined by OR. + +Each ACL declaration line must only contain a single ACL matching keyword, +followed by one or multiple pattern values. It's not allowed to use multiple +matching keywords and combine them by logical or/and operators in an ACL +declaration line. The use of ACLs provides a flexible solution to perform content switching and generally to take decisions based on content extracted from the request, the -- 2.47.3