azure-docs
azure-docs copied to clipboard
MicrosoftDocs
No information on Azure Front Door cache purging speed
There is currently no information on how long it takes for Azure Front Door to stop serving content from any POP after the Purge API call has completed. Since the Purge API call is a long running operation, one would assume that as soon as it completes it has been removed from all POPs, but this does not seem to be the case.
This information is crucial for determining whether Azure Front Door is a viable solution, or not. For some websites it might be acceptable if it takes half an hour, but for other websites a delay of 3 minutes might already be unacceptable.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 91ae4d86-3843-4e48-c1ce-625ee1fb0971
- Version Independent ID: 4e736e00-6d2d-70b4-5add-36a539853c1c
- Content: Cache purging - Azure Front Door
- Content Source: articles/frontdoor/standard-premium/how-to-cache-purge.md
- Service: frontdoor
- GitHub Login: @duongau
- Microsoft Alias: duau
@marklagendijk , thank you for your feedback. We'll review this and get back to you shortly!
@marklagendijk , We have assigned this to the content owner/author for review & update.
@duongau , I have looped you in the internal email where the backend team has provided some insights on this feedback. Please review the same and update the doc accordingly.
@GitaraniSharma-MSFT , @duongau it's been more than a month... any update?
@marklagendijk Apologies on the delayed response. Cache purging can take up to 10 minutes to propagate throughout the network and across all the edge locations. We'll have this information published later in that article.
Hello @marklagendijk, this information is now live. Thank you for bringing this to our attention. Please let me know if you have any other concerns. I will be closing this issue for now. #please-close