You may have faced some issues while securing App Services behind an Azure Application Gateway.
More often than not, these issues are not really caused due to problems with the App Service or Application Gateway itself, but with the way the configuration & functioning of these products/services are interpreted.
In this blog post, I'm calling out one such scenario where redirects configured at the App Service web.config, end up exposing *.azurewebsites.net to the client (for example, on the browser's address bar)
WHY IS THIS AN ISSUE?
HERE’S WHAT’S ACTUALLY HAPPENING:
A little about ‘PickHostNameFromBackendHttpSettings’ –
HOW DO WE FIX THIS?
Here’s a solution we can suggest our customers when the redirects at the backends cause such issues:
Solution – Ensure that any redirects respect the domain that the user has originally requested (i.e. the application gateway domain).
|Record Type||Host Name||Value|
I hope this helps! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.