Skip to content

CDNetworks Documentation

Managing Content permalink

CDN360 supports a content management purge function that allows you to override the cache time. This feature is handy when the content on your web server has changed and you want CDN360 to update its servers with your changes. For example, if your website has a cache time of one week, but you want your website visitors to see a new update to one of your pages, you can use the purge option to flush the cache and enable your visitors to view the new content.

Content management purge activities are performed from the Content Management page. To display this page, click Content Management in the left pane.

The following figure shows the key elements on the page, and the table following the figure describes them.

null

FieldsDescription
1To filter purges, type characters in this field and then press the Enter key. All purges that do not contain the typed characters are hidden. Filtering is not case-sensitive. To remove the filter, click the x icon at the right side of the search field.
2Each purge appears on its own row. Clicking an ID shows detailed information about the purge.
3Icon to filter purges by their submission date.
4The button to create purge requests.

Creating a Purge Request permalink

If the content on your origin web server has changed, request a purge to have CDN360 distribute those changes.

  1. In the left pane, click Content Management.
  2. At the top right of the page, click the Create Purge button.
  3. Complete the fields in the Purge form. Required fields are denoted by an asterisk (*). The top of the form shows the percentage of the daily purge quota that has been used.

purge form

FieldsDescription
Target EnvironmentSelect whether the purge will occur in the staging or production environment. Default is staging.
Purge ActionSelect whether you want the content deleted or invalidated.
  • Delete = removes the object from the cache of edge servers. The next time the edge server receives a request for the removed content, it retrieves the current version from your origin server. (default)
  • Invalidate = this is the default setting and marks the cached content as invalid. However, the content is not removed from cache and objects are not retrieved from your origin unless they are newer than the cached versions. With this setting, CDN360 edge servers can continue serving stale content to your end users if the origin cannot be reached.
Purge TypeSelect whether you want to purge a file or a directory. Default is file.
Add a file to be purgedIf Purge Type is set to File, select https:// (default) or http:// from the drop-down list, enter the name of the file to be purged, and then click Add File. Repeat this step for each additional file you want to purge. If you decide not to purge one or more files that you added, click the x icon at the right side of the file name.
Add a file purge headerIf Purge Type is set to File, specify the name and value of the HTTP request header included in the cache key, and then click Add Header. Repeat this step for each additional request header you want to purge. If you decide not to purge one or more request headers that you added, click the x icon at the right side of the header name.
Add a directory to be purgedIf Purge Type is set to Directory, select https:// (default) or http:// from the drop-down list, enter the name of the directory to be purged, and then click Add Directory. Note that subdirectories of the directory will also be purged. Repeat this step for each additional directory you want to purge. If you decide not to purge one or more directories that you added, click the x icon at the right side of the directory name.
  1. Click Start Purge.

Viewing Purge Details permalink

  1. In the left pane, click Content Management.
  2. Click the ID associated with the purge operation. A Purge Details form provides details about the selected purge operation.

Purge History permalink

  1. In the left pane, click Content Management.

  2. A Purge tab on the Content Management page shows details similar to those in the following figure:

    • ID associated with the purge request.
    • Hostname of the property associated with the purge request.
    • Target environment where the purge occurred (either Staging or Production).
    • Action that was performed (either Delete or Invalidate).
    • Number of files and directories purged.
    • Date and time when the purge request was submitted and completed.
    • A success rate indicator that shows a completion percentage from 0 to 100%.

null

  1. To specify the exact content you want to purge, create a purge request.