Skip to content

Commit a6435e8

Browse files
committed
move the note after the tabs section
1 parent 1332b2c commit a6435e8

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/web-application-firewall/afds/waf-front-door-configure-custom-response-code.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,6 @@ In the preceding example, we kept the response code as 403 and configured a shor
2828

2929
:::image type="content" source="../media/waf-front-door-configure-custom-response-code/custom-response.png" alt-text="Screenshot that shows a custom response example.":::
3030

31-
32-
> [!NOTE]
33-
> If you leave the block response body blank, the WAF will respond 403 (forbidden) on normal WAF blocks and will respond 429 (too many requests) on rate limit blocks.
34-
3531
# [**PowerShell**](#tab/powershell)
3632

3733
Follow these steps to configure a custom response status code and message by using PowerShell.
@@ -107,6 +103,9 @@ Update-AzFrontDoorFireWallPolicy `
107103

108104
---
109105

106+
> [!NOTE]
107+
> If you leave the block response body blank, the WAF will respond 403 (forbidden) on normal WAF blocks and will respond 429 (too many requests) on rate limit blocks.
108+
110109
::: zone pivot="front-door-standard-premium"
111110

112111
"{{azure-ref}}" inserts the unique reference string in the response body. The value matches the TrackingReference field in the `FrontDoorAccessLog` and `FrontDoorWebApplicationFirewallLog` logs.
@@ -122,4 +121,4 @@ Update-AzFrontDoorFireWallPolicy `
122121
## Next step
123122

124123
> [!div class="nextstepaction"]
125-
> [Configure a Web Application Firewall rate-limit rule](../afds/waf-front-door-rate-limit-configure.md).
124+
> [Configure a Web Application Firewall rate-limit rule](../afds/waf-front-door-rate-limit-configure.md)

0 commit comments

Comments
 (0)