Show search and navigation.

Edge CNAME

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: Request

Purpose: Identifies requests that point to a specific edge CNAME.

Key information:

The list of available edge CNAMEs is limited to those that have been configured on the Edge CNAMEs page corresponding to the platform on which Rules Engine is being configured.
Before attempting to delete an edge CNAME configuration, make sure that an Edge CNAME match condition does not reference it. Edge CNAME configurations that have been defined in a rule cannot be deleted from the Edge CNAMEs page.
Due to the manner in which cache settings are tracked, this match condition is incompatible with the following features:
- Complete Cache Fill (End-of-Life)
- Default Internal Max-Age
- Force Internal Max-Age
- Ignore Origin No-Cache
- Internal Max-Stale