Question

Your company runs a web application behind Azure Application Gateway v2. The backend application generates absolute redirect URLs (HTTP 302 responses with a Location header) using its internal hostname 'app-internal.contoso.local', which is what it receives in the incoming Host header because the HTTP settings override the hostname to the backend pool member's name. Users report that after login, they are redirected to a broken internal URL instead of the public site 'www.contoso.com'. You must ensure redirects point to the correct public hostname without modifying the backend application. What should you configure on the Application Gateway?

Accepted Answer

Create a rewrite rule set that rewrites the Location header in the response, replacing the internal hostname with 'www.contoso.com', and associate it with the routing rule.

Answer

Enable 'Pick host name from backend target' in the HTTP settings so the backend receives the public hostname.

Answer

Add a health probe with a custom host header set to 'www.contoso.com' and associate it with the HTTP settings.

Answer

Configure a multi-site listener with the host name 'www.contoso.com' and enable end-to-end TLS.