Hello,
I am setting up an Azure Application Gateway to route traffic to an Azure App Service, which is currently accessible via aladwaa360.azurewebsites.net
. I have also configured a custom domain for the gateway: staging.example.com
.
Issue 1: “502 Bad Gateway” with Host Name Override Disabled
When I access the Application Gateway’s public IP, I receive a “502 Bad Gateway” error if the ‘Override with new host name’ option in the backend settings is set to No. I’m not sure why this happens, as I expected the traffic to forward to my app service correctly.
Issue 2: URL Redirection Problem with Host Name Override Enabled
When I enable the ‘Override with new host name’ option, the gateway works and routes traffic correctly to my app service under the custom domain staging.example.com
. However, there is an issue after logging in to the app.
The app service has a login form that redirects users to another application hosted at staging.account.example.com/login
. After successfully logging in, the user should be redirected back to staging.example.com
, but the URL changes briefly to staging.example.com
and then quickly switches back to the app service’s default domain, aladwaa360.azurewebsites.net
.
Goal:
- I want to ensure that after logging in, the URL remains as
staging.example.com
without switching back to the default app service domain. I also plan to route traffic based on the URL path to different backends (e.g., traffic to/qrcode
should go to another app service).
Questions:
- Why does the “502 Bad Gateway” error occur when the “Override with new host name” option is disabled?
- How can I fix the redirection issue so that the browser stays on the custom domain
staging.example.com
after logging in, without redirecting to the app service’s default domain? - What is the best way to configure path-based routing in the Application Gateway for different backend services?
Thank you in advance for your help!