You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/web-application-firewall/ag/ag-overview.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,7 @@ The Azure web application firewall (WAF) engine is the component that inspects t
125
125
126
126
WAF customers can choose which action is run when a request matches a rules conditions. Below is the listed of supported actions.
127
127
128
+
* Allow: Request passes through the WAF and is forwarded to back-end. No further lower priority rules can block this request. Allow actions are only applicable to the Bot Manager ruleset, and are not applicable to the Core Rule Set.
128
129
* Block: The request is blocked and WAF sends a response to the client without forwarding the request to the back-end.
129
130
* Log: Request is logged in the WAF logs and WAF continues evaluating lower priority rules.
130
131
* Anomaly score: This is the default action for CRS ruleset where total anomaly score is incremented when a rule with this action is matched. Anomaly scoring is not applicable for the Bot Manager ruleset.
0 commit comments