Skip to content

Commit 7ba48db

Browse files
authored
Corrected spelling mistake in the document
Corrected the spelling mistake for the word "Visibility" in the document
1 parent e2e9d2e commit 7ba48db

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/web-application-firewall/afds/waf-front-door-drs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ If the anomaly score is 5 or greater, WAF blocks the request.
5555

5656
For example, a single *Critical* rule match is enough for the WAF to block a request, because the overall anomaly score is 5. However, one *Warning* rule match only increases the anomaly score by 3, which isn't enough by itself to block the traffic.
5757

58-
When your WAF uses older version of the default rule set (before DRS 2.0), your WAF runs in the traditional mode. Traffic that matches any rule is considered independently of any other rule matches. In traditional mode, you don't have visiblity into the complete set of rules that a specific request matched.
58+
When your WAF uses older version of the default rule set (before DRS 2.0), your WAF runs in the traditional mode. Traffic that matches any rule is considered independently of any other rule matches. In traditional mode, you don't have visibility into the complete set of rules that a specific request matched.
5959

6060
The version of the DRS that you use also determines which content types are supported for request body inspection. For more information, see [What content types does WAF support?](waf-faq.yml#what-content-types-does-waf-support-) in the FAQ.
6161

0 commit comments

Comments
 (0)