Skip to content

Commit 339c955

Browse files
authored
Merge pull request #111342 from vhorne/waf-custom
change equals to equal
2 parents 1f38cfa + e24284c commit 339c955

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/web-application-firewall/ag/custom-waf-rules-overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: web-application-firewall
55
ms.topic: article
66
author: vhorne
77
ms.service: web-application-firewall
8-
ms.date: 01/30/2020
8+
ms.date: 04/14/2020
99
ms.author: victorh
1010
---
1111

@@ -15,13 +15,13 @@ The Azure Application Gateway Web Application Firewall (WAF) v2 comes with a pre
1515

1616
Custom rules allow you to create your own rules that are evaluated for each request that passes through the WAF. These rules hold a higher priority than the rest of the rules in the managed rule sets. The custom rules contain a rule name, rule priority, and an array of matching conditions. If these conditions are met, an action is taken (to allow or block).
1717

18-
For example, you can block all requests from an IP address in the range 192.168.5.4/24. In this rule, the operator is *IPMatch*, the matchValues is the IP address range (192.168.5.4/24), and the action is to block the traffic. You also set the rules name and priority.
18+
For example, you can block all requests from an IP address in the range 192.168.5.4/24. In this rule, the operator is *IPMatch*, the matchValues is the IP address range (192.168.5.4/24), and the action is to block the traffic. You also set the rule's name and priority.
1919

2020
Custom rules support using compounding logic to make more advanced rules that address your security needs. For example, (Condition 1 **and** Condition 2) **or** Condition 3). This means that if Condition 1 **and** Condition 2 are met, **or** if Condition 3 is met, the WAF should take the action specified in the custom rule.
2121

22-
Different matching conditions within the same rule are always compounded using **and**. For example, block traffic from a specific IP address, and only if theyre using a certain browser.
22+
Different matching conditions within the same rule are always compounded using **and**. For example, block traffic from a specific IP address, and only if they're using a certain browser.
2323

24-
If you want to **or** two different conditions, the two conditions must be in different rules. For example, block traffic from a specific IP address or block traffic if theyre using a specific browser.
24+
If you want to **or** two different conditions, the two conditions must be in different rules. For example, block traffic from a specific IP address or block traffic if they're using a specific browser.
2525

2626
> [!NOTE]
2727
> The maximum number of WAF custom rules is 100. For more information about Application Gateway limits, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md#application-gateway-limits).
@@ -120,7 +120,7 @@ Describes the field of the matchVariable collection. For example, if the matchVa
120120
Must be one of the following operators:
121121

122122
- IPMatch - only used when Match Variable is *RemoteAddr*
123-
- Equals – input is the same as the MatchValue
123+
- Equal – input is the same as the MatchValue
124124
- Contains
125125
- LessThan
126126
- GreaterThan

0 commit comments

Comments
 (0)