ナビ付きでトピックを開く

 

Troubleshooting Customer Origin Delivery

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.

Purpose

The purpose of this procedure is to troubleshoot data delivery from a customer origin server.

Related Troubleshooting Articles:

Web Server Availability

A standard CDN setup requires web server availability for the delivery of staleIdentifies cached content whose TTL has expired. Our edge servers revalidate stale content with the origin server. This step ensures that the latest version of the requested content is served to the requester. content or content that has not been previously cached.

An assetA file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.'s caching policy determines whether stale content may be served when a customer origin serverRefers to a web server external to our network that will serve as the source from which content will be delivered. This type of web server must be defined in a customer origin configuration. is non-responsive. One way of defining this type of caching policy is through Rules Engine's Internal Max-Stale feature.

Checklist:

Verify web server availability by pinging each hostname/IP address defined in the customer origin configuration experiencing delivery issues.

URL Verification

A valid CDN or edge CNAME URL requires a specific syntax and case.

CDN URL Syntax:

[http|https]Support for the HTTP/HTTPS scheme may be enabled through a customer origin configuration. Additionally, the use of an HTTPS scheme requires a TLS certificate and an edge CNAME configuration.://[wpc|wac|adn]Identifies the platform where content will be served. The desired customer origin configuration must be defined on the selected platform..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}/80ANThis 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 assigned to the desired customer origin configuration./PathRepresents the relative path from a web server's virtual directory to the location where the requested content is stored.

Edge CNAME URL Syntax:

[http|https]Support for the HTTP/HTTPS scheme may be enabled through a customer origin configuration. Additionally, the use of an HTTPS scheme requires a TLS certificate and an edge CNAME configuration.://EdgeCNAMEHostnameRepresents the hostname assigned to an edge CNAME configuration./PathRepresents the relative path from a web server's virtual directory to the location where the requested content is stored.

Example:

This example scenario is based on the setup defined below.

Setup Description

Platform

HTTP Large

Customer origin name

myorigin

Relative path

/marketing/viral

File name

product.png

Valid CDN URL:

http://wpc.0001.omegacdn.net/800001/myorigin/marketing/viral/product.png

Invalid CDN URL #1:The syntax for this sample CDN URL is invalid since it omits the customer origin name from the CDN URL.

http://wpc.0001.omegacdn.net/800001/marketing/viral/product.png

Invalid CDN URL #2:This example demonstrates that CDN URLs are case-sensitive.

http://wpc.0001.omegacdn.net/800001/Myorigin/marketing/viral/Product.png

Checklist:

Verify the syntax and the case of the URL through which content is being requested.