Hello,
I have a web application configured with 3 deployment slots, each with a custom subdomain. I am trying to configure an application gateway to simply route to one of the slots (test.mydomain.com). The backend pool of the AG has just one FQDN, mydomain-testing.azurewebsite.net. End to end SSL is setup.
What I am finding is that when I enter "https://test.mydomain.com" in the browser, it is actually redirecting (and changing the URL) to (mydomain-testing.azurewebsite.net). My expectation, and what I see on numerous tutorials, is the URL should be retained as https://test.mydomain.com, rather than exposing the FQDN of the backend pool.
Is this expected behavior, or is there a limitation due to having a deployment slot FQDN as a backend pool member? Is there any way to retain the custom domain name?
Thanks,
Jack