Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
The WAF blocks our CDN making it impossible to use services like MaxCDN. Please Microsoft, allow your WAF to allow/disallow certain requests based upon much more flexible rules. Disabling the WAF is our only option. It is useless!!
We’ve moved this ask to the backlog due to technical challenges in reserving Public IP addresses during stop state.
Bump bump bump. Come on Azure, you are supposed to be state of the art!
This is an essential feature. Developers need a way to see the definitive client IP address. The X-Forwarded-For Header from the client should be overwritten by Azure with the definitive value. Multiple "hop" values do not help the developer. CloudFlare, for example, has a special header for this purpose. Azure should too.
It works for us - we see X-Forwarded-For OK, but we use X_FORWARDED_FOR on our platform.