Add new groupByVariables to Configure Rate Limit Custom Rules

[yaarark]

Related command
Add new groupByVariables to Configure Rate Limit Custom Rules https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/rate-limiting-configure?tabs=cli.
GeoLocationXffHeader, ClientAddrXffHeader.
For example:

az network application-gateway waf-policy custom-rule create --policy-name ExamplePolicy --resource-group ExampleRG --action Block --name ClientIPRateLimitRule --priority 90 --rule-type RateLimitRule --rate-limit-threshold 100 --group-by-user-session '[{'"groupByVariables"':[{'"variableName"':'"ClientAddrXffHeader"'}]}]'

az network application-gateway waf-policy custom-rule create --policy-name ExamplePolicy --resource-group ExampleRG --action Block --name ClientIPRateLimitRule --priority 90 --rule-type RateLimitRule --rate-limit-threshold 100 --group-by-user-session '[{'"groupByVariables"':[{'"variableName"':'"GeoLocationXffHeader"'}]}]'

Describe the solution you'd like

Add two variableName options to groupByVariables. GeoLocationXffHeader, ClientAddrXffHeader.

Additional context

Code changes will be part of NRP 187 and Appgw changes is part of 30.0 release. Swagger changes will be part of next release.

[yonzhan]

Thank you for opening this issue, we will look into it.

[yaarark]

@yonzhan any updates on this issue?

[k0eff]

Bumping up the feature request, Rate limiting through http headers in AppGw is something we would use as well.