CDN Origin

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.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Basic

Category: Origin

Purpose: Identifies requests for content stored on CDN storage.

This match condition does not identify requests for content stored on CDN Object Storage.

This match condition is met when the request URI leverages the content access pointThis URL segment of a CDN URL identifies where the request should be directed. This relative path starts directly after the CDN hostname. The proper syntax for a content access point is "/yyAN," where "yy" stands for the origin identifier and "AN" stands for a customer account number. A content access point for a customer origin also includes a directory that identifies it. (e.g., /000001) defined in this match condition.

CDN URL: The request URI must contain the selected content access point.
Edge CNAME URL: The corresponding edge CNAME configuration must point to the selected content access point.

The content access point identifies the service that should serve the requested content.

A rule should not contain multiple origin match conditions (i.e., CDN Origin and Customer Origin). This type of configuration would create a match pattern that could never be satisfied.
An exception occurs when using else if statements via the "Select First Match" option.

Example

The following sample configuration assumes that this match condition is satisfied when a request matches the specified value.

Setting this match condition to "/000001" will match the following request:

http://wpc..omegacdn.net/000001/marketing/images/event1.jpg

However, it will not match against the following request for content on CDN Object Storage:

http://wpc..omegacdn.net/300001/marketing/event.m3u8