Skip to content

Commit 15514a5

Browse files
Merge pull request #292956 from vhorne/waf-excl-list
freshness review
2 parents cca2927 + c3b3374 commit 15514a5

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/web-application-firewall/ag/application-gateway-waf-configuration.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article provides information on Web Application Firewall exclu
44
services: web-application-firewall
55
author: vhorne
66
ms.service: azure-web-application-firewall
7-
ms.date: 05/17/2023
7+
ms.date: 01/13/2025
88
ms.author: victorh
99
ms.topic: concept-article
1010
ms.custom: devx-track-azurepowershell
@@ -37,9 +37,9 @@ You can specify an exact request header, body, cookie, or query string attribute
3737
- **Starts with**: This operator matches all fields that start with the specified selector value.
3838
- **Ends with**: This operator matches all request fields that end with the specified selector value.
3939
- **Contains**: This operator matches all request fields that contain the specified selector value.
40-
- **Equals any**: This operator matches all request fields. * will be the selector value. For example, you would use this operator when you don't know the exact values for a given match variable but want to make sure that the request traffic still gets excluded from rules evaluation.
40+
- **Equals any**: This operator matches all request fields. * is the selector value. For example, you would use this operator when you don't know the exact values for a given match variable but want to make sure that the request traffic still gets excluded from rules evaluation.
4141

42-
When processing exclusions the WAF engine performs a case sensitive/insensitive match based on the below table. Additionally, regular expressions aren't allowed as selectors and XML request bodies aren't supported.
42+
When processing exclusions the WAF engine performs a case sensitive/insensitive match based on the following table. Additionally, regular expressions aren't allowed as selectors and XML request bodies aren't supported.
4343

4444
| Request Body Part | CRS 3.1 and Earlier | CRS 3.2 and Later |
4545
|-|-|-|
@@ -77,7 +77,7 @@ In contrast, if your WAF detects the header's name (`My-Header`) as an attack, y
7777

7878
#### Request attribute examples
7979

80-
The below table shows some examples of how you might structure your exclusion for a given match variable.
80+
The following table shows some examples of how you might structure your exclusion for a given match variable.
8181

8282
| Attribute to Exclude | matchVariable | selectorMatchOperator | Example selector | Example request | What gets excluded |
8383
|-|-|-|-|-|-|
@@ -526,7 +526,7 @@ resource wafPolicy 'Microsoft.Network/ApplicationGatewayWebApplicationFirewallPo
526526

527527
---
528528

529-
So if the URL `http://www.contoso.com/?user%3c%3e=joe` is scanned by the WAF, it won't evaluate the string **joe**, but it still evaluates the parameter name **user%3c%3e**.
529+
So if the URL `http://www.contoso.com/?user%3c%3e=joe` is scanned by the WAF, it doesn't evaluate the string **joe**, but it still evaluates the parameter name **user%3c%3e**.
530530

531531
## Next steps
532532

0 commit comments

Comments
 (0)