Skip to content

Commit d07c2b7

Browse files
committed
freshness review
1 parent 04bffa4 commit d07c2b7

File tree

5 files changed

+27
-29
lines changed

5 files changed

+27
-29
lines changed

articles/cdn/cdn-purge-endpoint.md

Lines changed: 27 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -4,51 +4,49 @@ description: Learn how to purge all cached content from an Azure Content Deliver
44
services: cdn
55
documentationcenter: ''
66
author: duongau
7-
manager: danielgi
8-
editor: sohamnchatterjee
9-
7+
manager: kumud
108
ms.assetid: 0b50230b-fe82-4740-90aa-95d4dde8bd4f
119
ms.service: azure-cdn
1210
ms.workload: tbd
1311
ms.tgt_pltfrm: na
1412
ms.topic: how-to
15-
ms.date: 06/30/2021
13+
ms.date: 02/21/2023
1614
ms.author: duau
1715

1816
---
17+
1918
# Purge an Azure CDN endpoint
20-
## Overview
21-
Azure CDN edge nodes will cache assets until the asset's time-to-live (TTL) expires. After the asset's TTL expires, when a client requests the asset from the edge node, the edge node will retrieve a new updated copy of the asset to serve the client request and store refresh the cache.
2219

23-
The best practice to make sure your users always obtain the latest copy of your assets is to version your assets for each update and publish them as new URLs. CDN will immediately retrieve the new assets for the next client requests. Sometimes you may wish to purge cached content from all edge nodes and force them all to retrieve new updated assets. This might be due to updates to your web application, or to quickly update assets that contain incorrect information.
20+
Azure CDN edge nodes cache contents until the content's time-to-live (TTL) expires. After the TTL expires, when a client makes a request for the content from the edge node, the edge node will retrieve a new updated copy of the content to serve to the client. Then the refreshed content in cache of the edge node.
21+
22+
The best practice to make sure your users always obtain the latest copy of your assets is to version your assets for each update and publish them as new URLs. CDN will immediately retrieve the new assets for the next client requests. Sometimes you may wish to purge cached content from all edge nodes and force them all to retrieve new updated assets. The reason might be due to updates to your web application, or to quickly update assets that contain incorrect information.
2423

2524
> [!TIP]
2625
> Note that purging only clears the cached content on the CDN edge servers. Any downstream caches, such as proxy servers and local browser caches, may still hold a cached copy of the file. It's important to remember this when you set a file's time-to-live. You can force a downstream client to request the latest version of your file by giving it a unique name every time you update it, or by taking advantage of [query string caching](cdn-query-string.md).
27-
>
28-
>
26+
>
2927
30-
This tutorial walks you through purging assets from all edge nodes of an endpoint.
28+
This guide walks you through purging assets from all edge nodes of an endpoint.
3129

32-
## Walkthrough
33-
1. In the [Azure Portal](https://portal.azure.com), browse to the CDN profile containing the endpoint you wish to purge.
34-
2. From the CDN profile blade, click the purge button.
35-
36-
![CDN profile blade](./media/cdn-purge-endpoint/cdn-profile-blade.png)
37-
38-
The Purge blade opens.
39-
40-
![CDN purge blade](./media/cdn-purge-endpoint/cdn-purge-blade.png)
41-
3. On the Purge blade, select the service address you wish to purge from the URL dropdown.
30+
## Purge contents from an Azure CDN endpoint
31+
32+
1. In the [Azure portal](https://portal.azure.com), browse to the CDN profile containing the endpoint you wish to purge.
33+
34+
1. From the CDN profile page, select the purge button.
35+
36+
:::image type="content" source="./media/cdn-purge-endpoint/cdn-profile-blade.png" alt-text="Screenshot of the overview page for an Azure CDN profile.":::
4237

43-
![Purge form](./media/cdn-purge-endpoint/cdn-purge-form.png)
38+
1. On the Purge page, select the service address you wish to purge from the URL dropdown.
39+
40+
:::image type="content" source="./media/cdn-purge-endpoint/cdn-purge-form.png" alt-text="Alt text here.":::
4441

4542
> [!NOTE]
46-
> You can also get to the Purge blade by clicking the **Purge** button on the CDN endpoint blade. In that case, the **URL** field will be pre-populated with the service address of that specific endpoint.
47-
>
43+
> You can also get to the purge page by clicking the **Purge** button on the CDN endpoint blade. In that case, the **URL** field will be pre-populated with the service address of that specific endpoint.
4844
>
49-
4. Select what assets you wish to purge from the edge nodes. If you wish to clear all assets, click the **Purge all** checkbox. Otherwise, type the path of each asset you wish to purge in the **Path** textbox. Below formats are supported in the path.
50-
1. **Single URL purge**: Purge individual asset by specifying the full URL, with or without the file extension, e.g.,`/pictures/strasbourg.png`; `/pictures/strasbourg`
51-
2. **Wildcard purge**: Asterisk (\*) may be used as a wildcard. Purge all folders, sub-folders and files under an endpoint with `/*` in the path or purge all sub-folders and files under a specific folder by specifying the folder followed by `/*`, e.g.,`/pictures/*`. Note that wildcard purge is not supported by Azure CDN from Akamai currently.
45+
46+
1. Select what assets you wish to purge from the edge nodes. If you wish to clear all assets, select the **Purge all** checkbox. Otherwise, type the path of each asset you wish to purge in the **Path** textbox. The following formats for paths are supported:
47+
48+
1. **Single URL purge**: Purge individual asset by specifying the full URL, with or without the file extension, for example,`/pictures/strasbourg.png`; `/pictures/strasbourg`
49+
2. **Wildcard purge**: You can use an asterisk (\*) 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/*`. Wildcard purge isn't supported by Azure CDN from Akamai currently.
5250
3. **Root domain purge**: Purge the root of the endpoint with "/" in the path.
5351

5452
> [!TIP]
@@ -62,7 +60,7 @@ This tutorial walks you through purging assets from all edge nodes of an endpoin
6260
>
6361
> 1. In Azure CDN from Microsoft, query strings in the purge URL path are not considered. If the path to purge is provided as `/TestCDN?myname=max`, only `/TestCDN` is considered. The query string `myname=max` is omitted. Both `TestCDN?myname=max` and `TestCDN?myname=clark` will be purged.
6462
65-
5. Click the **Purge** button.
63+
5. Select the **Purge** button.
6664

6765
![Purge button](./media/cdn-purge-endpoint/cdn-purge-button.png)
6866

@@ -71,7 +69,7 @@ This tutorial walks you through purging assets from all edge nodes of an endpoin
7169
>
7270
>
7371
74-
## See also
72+
## Next steps
73+
7574
* [Pre-load assets on an Azure CDN endpoint](cdn-preload-endpoint.md)
7675
* [Azure CDN REST API reference - Purge or Pre-Load an Endpoint](/rest/api/cdn/endpoints)
77-
42.1 KB
Loading
Binary file not shown.
12.3 KB
Loading
8.75 KB
Loading

0 commit comments

Comments
 (0)