Purging Individual Assets from Azure Front Door Cache

Purge Individual Assets from Front Door Cache

Question

You are developing an ASP.NET Core website that uses Azure FrontDoor.

The website is used to build custom weather data sets for researchers.

Data sets are downloaded by users as Comma Separated Value (CSV) files.

The data is refreshed every 10 hours.

Specific files must be purged from the FrontDoor cache based upon Response Header values.

You need to purge individual assets from the Front Door cache.

Which type of cache purge should you use?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C.

A.

These formats are supported in the lists of paths to purge: -> Single path purge: Purge individual assets by specifying the full path of the asset (without the protocol and domain), with the file extension, for example, / [1] -> Wildcard purge: Asterisk (*) may be used as a wildcard.

Purge all folders, subfolders, and files under an endpoint with /* in the path or purge all subfolders and files under a specific folder by specifying the folder followed by /*, for example, /pictures/*

-> Root domain purge: Purge the root of the endpoint with "/" in the path.

https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching

To purge individual assets from the Azure FrontDoor cache, you should use the "single path" cache purge type.

Azure Front Door is a global service that offers traffic acceleration, routing, and load balancing for various types of web applications. It also offers caching capabilities that allow frequently accessed content to be stored closer to users, reducing latency and improving performance.

When content is cached, it is stored on FrontDoor servers around the world. Cache purging is the process of removing cached content from these servers to ensure that users receive the most up-to-date content.

There are three types of cache purges in Azure FrontDoor:

  • Single path: purges a specific URL or path from the cache.
  • Wildcard: purges all URLs that match a specified pattern.
  • Root domain: purges all content associated with a specific root domain.

In this scenario, since you need to purge specific files from the cache based on Response Header values, the most appropriate option would be the "single path" purge. This allows you to specify the exact URL or path of the file you want to remove from the cache.

To perform a single path cache purge in Azure FrontDoor, you can use the Azure portal or the Azure FrontDoor REST API. You will need to provide the URL or path of the file to be purged, as well as the FrontDoor endpoint to target.

For example, to purge the file "data.csv" from the cache for a FrontDoor endpoint named "myfrontdoorendpoint.azurefd.net", you could use the following API call:

javascript
POST https://myfrontdoorendpoint.azurefd.net/purge/data.csv

This will instruct Azure FrontDoor to remove the specified file from the cache, ensuring that users receive the most up-to-date data when downloading the CSV file.