Skip to content

Commit 53dc23e

Browse files
committed
add link to rule processing detail section
1 parent 3cef393 commit 53dc23e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/application-gateway/configuration-request-routing-rules.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: application-gateway
77
ms.topic: conceptual
8-
ms.date: 09/09/2020
8+
ms.date: 04/25/2023
99
ms.author: greglin
1010
---
1111

@@ -24,6 +24,8 @@ When you create a rule, you choose between [*basic* and *path-based*](./applicat
2424

2525
For the v1 and v2 SKU, pattern matching of incoming requests is processed in the order that the paths are listed in the URL path map of the path-based rule. If a request matches the pattern in two or more paths in the path map, the path that's listed first is matched. And the request is forwarded to the back end that's associated with that path.
2626

27+
If you have multiple listeners, it is even more important that rules are processed in the correct order so that client traffic is received by the correct listener. For more information about rules evaluation order, see [Request Routing rules evaluation order](multiple-site-overview.md#request-routing-rules-evaluation-order).
28+
2729
## Associated listener
2830

2931
Associate a listener to the rule so that the *request-routing rule* that's associated with the listener is evaluated to determine the backend pool to route the request to.

0 commit comments

Comments
 (0)