Azure front Door url rewriting

Arthur(Xueli) Wang 0

We are migrating from Azure CDN to Azure Front Door and are encountering URL rewrite issues. Previously, in CDN, we could use (.*) to replace the matched content with a new address, while preserving any unmatched content and appending a SAS token to the end. Now, we must use {url_path:seg#} to match the corresponding content. For example, /content/* needs to be rewritten to /media/pdf/*?<SAS token>. How can we achieve this in Azure Front Door?

Thanks

Rohith Vinnakota 2,330 Reputation points Microsoft Vendor

2025-02-05T07:30:08.6133333+00:00
Hi @Arthur(Xueli) Wang,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I did a lab and I was successfully able to achieve this.

ADF logs

As you can see, the original request from client was <AFDEndPoint>/content/HTML/index.html?<SASToken>

But the request that went to the Storage Account was <StorageAccountName>.blob.core.windows.net:443/content/HTML/index.html?<SASToken>

{url_path:seg#}: Allow users to capture and use the desired URL path segment in URL Redirect, URL Rewrite, or any meaningful action.For a multiple-segment capture, when the source pattern is /id/12345/default/location/test, a URL rewrite destination /{url_path:seg1:3}/home results in /12345/default/location/home.

For more information,

URL Rewrite : https://learn.microsoft.com/en-us/azure/frontdoor/front-door-url-rewrite?pivots=front-door-standard-premium

Server Variables in Rule Sets : https://learn.microsoft.com/en-us/azure/frontdoor/rule-set-server-variables#server-variable-format

Kindly let us know if this helps or you need further assistance on this issue.

Share via

Azure front Door url rewriting

Your answer