0

I have an azure front door which has custom frontends/domains, backend-pools, and routing rules configured to use azure web apps as backends. When i go the website the request passes through front door as it should and picks the best available backend, but it displays the azure webapp's url on the browser from the backend pool and not the azure front door domain. I expect to have the frontend/domain in the browser when i am directed to the backend and do not display the azure web app's url in the browser.

For example, when i go to www.mysite.com, i want it to be like www.mysite.com/foo (displaying the content from backend web app) and not mywebapp.azurewebsites.net/foo

Any guidance on how it can be achieved or is it possible to achieve?

Takhi
  • 335
  • 1
  • 4
  • 18

2 Answers2

0

The Azure front door just does a simple URL forwarding for the incoming client traffic. After my validation, if we select the forwarding protocol to HTTPS only, the address bar will not display the backend URL when you access the front door URL.

enter image description here

However, you actually still see the real backend domain in the set-cookie.

enter image description here

For more information, you could read the Backend host header and a similar question here1 and here2.

Nancy
  • 26,865
  • 3
  • 18
  • 34
  • My current setting is already the way you mentioned above. – Takhi Dec 09 '20 at 07:55
  • As far as I know, it's not possible to achieve the requirements with front door, like www.mysite.com/foo (displaying the content from backend web app) and not mywebapp.azurewebsites.net/foo. Instead, the Azure application gateway can achieve it by working as a reverse proxy. – Nancy Dec 09 '20 at 07:59
0

THis is possible using the forward feature in AFD, but if you are using redirects then the actual backend URL will be shown of course, so configure basic Forwarding and the AFD URL is the one that will be shown at all times

Matt Douhan
  • 677
  • 3
  • 13