From 1f7a4174bace31eb1c3d711a27c79f3654692009 Mon Sep 17 00:00:00 2001 From: Ludovic Fernandez Date: Fri, 30 Nov 2018 09:08:03 +0100 Subject: [PATCH] Matcher associativity rule. --- docs/basics.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/basics.md b/docs/basics.md index 936b7bd71..170f5a210 100644 --- a/docs/basics.md +++ b/docs/basics.md @@ -94,10 +94,12 @@ Following is the list of existing modifier rules: Matcher rules determine if a particular request should be forwarded to a backend. -Separate multiple rule values by `,` (comma) in order to enable ANY semantics (i.e., forward a request if any rule matches). -Does not work for `Headers` and `HeadersRegexp`. - -Separate multiple rule values by `;` (semicolon) in order to enable ALL semantics (i.e., forward a request if all rules match). +The associativity rule is the following: +- `,` is the `OR` operator (works **only inside a matcher**, ex: `Host:foo.com,bar.com`). + - i.e., forward a request if any rule matches. + - Does not work for `Headers` and `HeadersRegexp`. +- `;` is the `AND` operator (works **only between matchers**, ex: `Host:foo.com;Path:/bar`) + - i.e., forward a request if all rules match Following is the list of existing matcher rules along with examples: