Show search and navigation.

Customer 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

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. - Advanced

Category: Origin

Purpose: Identifies requests for content stored on a customer origin server.

Key information:

This match condition will be satisfied regardless of whether content is requested using a CDN or an edge CNAME URL that points to the selected customer origin.
A customer origin configuration referenced by a rule may not be deleted from the Customer Origin page. Before attempting to delete a customer origin configuration, make sure that the following configurations do not reference it:
- Customer Origin match condition
- An edge CNAME configuration.
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.