Media Player

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

Once the desired media content is hosted on a customer or CDN origin server, you are ready to set up your media player for use with HTTP Progressive Download. This requires that you set the player URL to a CDN or edge CNAME URL that leverages the HTTP Large platform (as indicated below).

CDN URL:
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}/yyANThis term represents your customer account number (e.g., 0001) which can be found in the upper right-hand corner of the MCC./Path/Filename
Edge CNAME URL:
http://cname.domain.com/Path/Filename

When defining a CDN URL, you should keep the following items in mind:

Origin identifier: The term yy should be replaced with one of the following:
- Customer origin server: It should be replaced with "80" (e.g., /800001).
- CDN origin server: It should be replaced with "00" (e.g., /000001).
Path: Replace this term with the path to the folder where the desired media content is stored.
- Customer origin server: The specified path should start with the name of the customer origin configuration that points to your origin server.
Filename: Replace this term with the filename of the desired media asset (e.g., video.mp4).
Token-Based Authentication: If the desired video has been secured by Token-Based Authentication, then you will need to append to the file name a question mark (?) followed by a token valueFor example, if the file name is "video.mp4" and the desired token is "a4fbc3710fd3449a7c99984d1b86603c22be1006d830b," then you would specify "video.mp4?a4fbc3710fd3449a7c99984d1b86603c22be1006d830b" as your file name. that corresponds to an encryption key. Learn more about Token-Based Authentication.

Learn how to create an alias to a CDN URL through the use of an edge CNAME.