Azure front door routing multiple Static Web Apps with common azure front door domain name

Sakkaravarthy Muniyasamy - Contractor 10

I have 3 Azure static web apps with different domain names, for example,

www.application1.com, www.application2.com, and www.application3.com.

I want to configure these apps in Azure's front door with the domain "www.common.com" and all the apps must be navigated through

I have created origin and routes (Pattern application1 to the origin www.application1.com) Azure Front Door for each app having path www.common.com/application1,

The Azure front door always takes me to www.application1.com when I navigate to the URL www.common.com/application1.

I want to keep the domain name of Azure front door (www.common.com/application1 ) in the browser instead of redirecting the user to www.application1.com

ChaitanyaNaykodi-MSFT 26,546 Reputation points Microsoft Employee

2024-05-15T22:25:35.3866667+00:00

@Sakkaravarthy Muniyasamy - Contractor

Thank you for posting a detailed question here.

As documented here

Custom domains: Now that Front Door is managing your site, you no longer use the Azure Static Web Apps custom domain feature. Azure Front Door has a separate process for adding a custom domain. Refer to Add a custom domain to your Front Door. When you add a custom domain to Front Door, you'll need to update your static web app configuration file to include it in the allowedForwardedHosts list.

Can you please confirm if you have added the custom domain to the allowedForwardedHosts list?

Thank you!
Sakkaravarthy Muniyasamy - Contractor 10 Reputation points

2024-05-15T22:52:26.6933333+00:00

ChaitanyaNaykodi-MSFT I want to use the Azure front door act as a reverse proxy. Currently, the Azure front door automatically redirects to the Azure Static web app URL. ( The domain name in the browser has been updated)

I am trying to have one single domain name for 3 different static web apps through Azure's front door.

In this case, the end user browser must be shown www.common.com/application1 instead of www.application1.com.

and, the domain name for www.application2.com must be www.common.com/application2.
Sakkaravarthy Muniyasamy - Contractor 10 Reputation points

2024-05-15T23:14:31.9533333+00:00

@ChaitanyaNaykodi-MSFT , Please share your email id. If you can help me over the email?
ChaitanyaNaykodi-MSFT 26,546 Reputation points Microsoft Employee

2024-05-16T23:12:43.85+00:00

@Sakkaravarthy Muniyasamy - Contractor Thank you for getting back. In order to further troubleshoot this issue. Can you share a screenshot of the route configuration for your set-up and any rule-engine rules associated with it?

At a glance this behavior might because of Preserving the original HTTP host name between a reverse proxy and its back-end web application as your issue coincides with the Potential problems described here but the article does not delve in static web apps just web apps. It will help if you could share the information requested above. Thanks

Please share your email id. If you can help me over the email?

For offline help it is recommended to create a support ticket with us.

Thanks
Sakkaravarthy Muniyasamy - Contractor 10 Reputation points

2024-05-16T23:46:10.53+00:00

ChaitanyaNaykodi-MSFT,

Below is the screenshot of our test Azure front door -(I used Azure Front Door Classic to check it works, both Azure Front Door Classic and the front door had the same result)

My Azure Static WebApp: This is the test web app I want to configure as an Origin in Azure front door service.

Azure Front Door Backend Pool for App4(I had created 4 backend pools for each static Web app).

Routing Rule for App4: i wanted to load the static web app with URL https:/AfdRURL/Pod4/

When I Navigate with the Azure front door URL: The static web page does not load and results in 404 error. Please refer to image 1 page loads work with actual static web app URL.
Sakkaravarthy Muniyasamy - Contractor 10 Reputation points

2024-05-16T23:49:17.82+00:00

ChaitanyaNaykodi-MSFT, Please check above details and help me to resolve the issue,
Sakkaravarthy Muniyasamy - Contractor 10 Reputation points

2024-05-16T23:49:37.4833333+00:00

ChaitanyaNaykodi-MSFT, Please check above details and help me to resolve the issue
Sivasankar Thalavai 0 Reputation points

2024-10-17T05:34:22.7933333+00:00

am also having similar requirement, is there any documentation link?

1 answer

ChaitanyaNaykodi-MSFT 26,546 Reputation points Microsoft Employee

2024-05-17T16:09:50.3766667+00:00

@Sakkaravarthy Muniyasamy - Contractor

Thank you for sharing the requested details here. I see that you have set Health Probe Path above to /assets/*Can you change this path to some definite for example to /assets/test.aspx ? I do not think wildcard will be supported in the health probe path.

Snippet from your question above:

As documenetd here "A 200 OK status code indicates the origin is healthy. Any other status code is considered a failure. If for any reason a valid HTTP response isn't received for a probe, the probe is counted as a failure."

So, in your case above the health probe will be sent to /assets/* path which will not return a 200 response. It is also recommended that you follow this best practices document here for health probe endpoints

Hope this helps. Please let me know if the issue still persists. Thanks
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure front door routing multiple Static Web Apps with common azure front door domain name

1 answer

Your answer