Skip to content

Commit 02171ae

Browse files
committed
Merge branch 'patch-51' of https://github.com/Miskatonic-Electronic/azure-docs-pr into fd-headers2
2 parents a53c98c + f0eb40a commit 02171ae

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/frontdoor/standard-premium/how-to-add-security-headers.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: frontdoor
55
author: duongau
66
ms.service: azure-frontdoor
77
ms.topic: how-to
8-
ms.date: 08/31/2023
8+
ms.date: 02/24/2025
99
ms.author: yuajia
1010
---
1111

@@ -35,6 +35,9 @@ The following example shows you how to add a Content-Security-Policy header to a
3535
> [!NOTE]
3636
> In this scenario, we did not add [match conditions](concept-rule-set-match-conditions.md) to the rule. All incoming requests that match the path defined in the associated route will have this rule applied. If you would like it to only apply to a subset of those requests, be sure to add your specific **match conditions** to this rule.
3737
38+
> [!NOTE]
39+
> If you are using Web Application Firewall (WAF) with your Azure Front Door, and the WAF blocks a request, HSTS headers will not be added to the request even if they are enabled on the Azure Front Door.
40+
3841
## Clean up resources
3942

4043
### Deleting a Rule

0 commit comments

Comments
 (0)