Content streamed over Dynamic Cloud Packaging may be purged from our network. Purging this type of content:
The following types of files are generated by Dynamic Cloud Packaging:
A player URL typically points to a master manifest file. This means that purging the player URL will not purge the majority of the content that was published by an encoder. In order to properly purge this content, the entire publishing location should be purged. This type of purge request is achieved through the use of a recursive purge (i.e., /*).
Purge syntax is provided below.
Live Streaming:
http://wpc.ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC..{Base Domain}/24ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC./Instance/*
On-Demand Streaming (CDN Storage):
http://wpc.ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC..{Base Domain}/04ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC./PathThis term represents the relative path to the directory containing the assets that were played back./*
On-Demand Streaming (Customer Origin):
http://wpc.ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC..{Base Domain}/84ANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC./CustomerOriginRepresents the name of the desired customer origin configuration./PathThis term represents the relative path to the directory containing the assets that were played back./*
Key information:
The following example demonstrates how to purge a live event.
Player URL:
Purge the instance:
Edgecast CDN