Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc]: New-AzFirewallPolicyApplicationRuleCustomHttpHeader #24817

Open
Lycrosa opened this issue May 6, 2024 · 1 comment
Open

[Doc]: New-AzFirewallPolicyApplicationRuleCustomHttpHeader #24817

Lycrosa opened this issue May 6, 2024 · 1 comment
Labels
customer-reported Network - Firewall question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@Lycrosa
Copy link

Lycrosa commented May 6, 2024

Type of issue

Missing information

Feedback

Hello,

I found documentation to this command: New-AzFirewallPolicyApplicationRuleCustomHttpHeader

https://learn.microsoft.com/en-us/powershell/module/az.network/new-azfirewallpolicyapplicationrulecustomhttpheader?view=azps-11.5.0

This explains the command, but I can't seem to find any documentation as to what this does. I don't even see that this feature exists besides that command. My Expectation is I Create this header and add it to an application rule. Then when this rule is hit the firewall will insert the header. However this doesn't seem to work. My guess is I am doing something wrong, but I have no idea what. Could you maybe add more information on how exactly this works?

For reference, here the application rule I created:

SourceAddresses         : {*}
TargetFqdns             : {login.microsoftonline.com, login.microsoft.com, login.windows.net}
FqdnTags                : {}
Protocols               : {Microsoft.Azure.Commands.Network.Models.PSAzureFirewallPolicyApplicationRuleProtocol,
                          Microsoft.Azure.Commands.Network.Models.PSAzureFirewallPolicyApplicationRuleProtocol}
SourceIpGroups          : {}
WebCategories           : {}
TargetUrls              : {}
TerminateTLS            : True
HttpHeadersToInsert     : {Restrict-Access-To-Tenants, Restrict-Access-Context}
Description             :
ProtocolsText           : [
                            {
                              "protocolType": "Http",
                              "port": 80
                            },
                            {
                              "protocolType": "Https",
                              "port": 443
                            }
                          ]
SourceAddressesText     : [
                            "*"
                          ]
SourceIpGroupsText      : []
TargetFqdnsText         : [
                            "login.microsoftonline.com",
                            "login.microsoft.com",
                            "login.windows.net"
                          ]
FqdnTagsText            : []
WebCategoriesText       : []
TargetUrlsText          : []
HttpHeadersToInsertText : [
                            {
                              "headerName": "Restrict-Access-To-Tenants",
                              "headerValue": "111fd61c-a2a5-4514-8a8a-f923d46b9b79"
                            },
                            {
                              "headerName": "Restrict-Access-Context",
                              "headerValue": "111fd61c-a2a5-4514-8a8a-f923d46b9b79"
                            }
                          ]
Name                    : restricttenant
RuleType                : ApplicationRule

Page URL

No response

Content source URL

No response

Author

No response

Document Id

No response

@Lycrosa Lycrosa added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label May 6, 2024
@isra-fel isra-fel added Service Attention This issue is responsible by Azure service team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Network - Firewall and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 7, 2024
@Alex-wdy
Copy link
Contributor

@gopimsft @gimotwanMSFT can you look at this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Network - Firewall question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants