Skip to content

Commit bc6f428

Browse files
committed
Remove unnecessary example
1 parent 4cf8daa commit bc6f428

File tree

1 file changed

+0
-57
lines changed

1 file changed

+0
-57
lines changed

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

Lines changed: 0 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -491,63 +491,6 @@ Corresponding JSON:
491491
}
492492
```
493493

494-
Alternative Azure PowerShell:
495-
496-
```azurepowershell
497-
$variable1 = New-AzApplicationGatewayFirewallMatchVariable `
498-
-VariableName RequestUri
499-
$condition1 = New-AzApplicationGatewayFirewallCondition `
500-
-MatchVariable $variable1 `
501-
-Operator Contains `
502-
-MatchValue "1=1" `
503-
-NegationCondition $False
504-
505-
$rule1 = New-AzApplicationGatewayFirewallCustomRule `
506-
-Name myrule1 `
507-
-Priority 10 `
508-
-RuleType MatchRule `
509-
-MatchCondition $condition1 `
510-
-Action Block
511-
512-
$variable2 = New-AzApplicationGatewayFirewallMatchVariable `
513-
-VariableName RequestUri
514-
515-
$condition2 = New-AzApplicationGatewayFirewallCondition `
516-
-MatchVariable $variable2 `
517-
-Operator Contains `
518-
-MatchValue "drop tables" `
519-
-NegationCondition $False
520-
521-
$rule2 = New-AzApplicationGatewayFirewallCustomRule `
522-
-Name myrule2 `
523-
-Priority 20 `
524-
-RuleType MatchRule `
525-
-MatchCondition $condition2 `
526-
-Action Block
527-
528-
$variable3 = New-AzApplicationGatewayFirewallMatchVariable `
529-
-VariableName RequestUri
530-
531-
$condition3 = New-AzApplicationGatewayFirewallCondition `
532-
-MatchVariable $variable3 `
533-
-Operator Contains `
534-
-MatchValue "’—" `
535-
-NegationCondition $False
536-
537-
$rule3 = New-AzApplicationGatewayFirewallCustomRule `
538-
-Name myrule3 `
539-
-Priority 30 `
540-
-RuleType MatchRule `
541-
-MatchCondition $condition3 `
542-
-Action Block
543-
```
544-
545-
Corresponding JSON:
546-
547-
```json
548-
TODO check this example
549-
```
550-
551494
## Example 7
552495

553496
It is not uncommon to see Azure Front Door deployed in front of Application Gateway. In order to make sure the traffic received by Application Gateway comes from the Front Door deployment, the best practice is to check if the `X-Azure-FDID` header contains the expected unique value. For more information on this, please see [How to lock down the access to my backend to only Azure Front Door](../../frontdoor/front-door-faq.yml#how-do-i-lock-down-the-access-to-my-backend-to-only-azure-front-door-)

0 commit comments

Comments
 (0)