Troubleshooting 404 Not Found

Purpose

The purpose of this procedure is to troubleshoot 404 Not Found responses. A 404 Not Found indicates that the requested content was not found on the origin server.

Case-Sensitive Requests

All CDN requests (i.e., CDN URLA system-defined URL that points to a CDN hostname. A CDN URL allows content delivery via our network. Simplify your CDN setup by also creating an edge CNAME configuration which potentially allows you to deliver traffic via the CDN using the same links as your current setup. and edge CNAME URLThis type of URL takes advantage of an edge CNAME configuration and a CNAME record to provide a friendlier alternative to a CDN URL. An edge CNAME URL is specific to the platform from which it was configured.) are case-sensitive.

For example, all of the following requests point to different assets:

• http://wpc.ABC1.omegacdn.net/00ABC1/MyFolder/asset.htm
• http://wpc.ABC1.omegacdn.net/00ABC1/MyFolder/Asset.htm
• http://wpc.ABC1.omegacdn.net/00ABC1/myfolder/asset.htm
• http://cdn.mydomain.com/myfolder/asset.HTM

Checklist:

Verify that the requested URL uses the proper caseCDN and edge CNAME URLs are case-sensitive. .

• Use a SFTP client to browse to the content in question. Compare the case used in the relative path and file name to the requested URL.

Customer Origin Server

Narrow down the source of the issue by requesting the asset directly from the origin server. Make sure that this request uses the same relative path and file name as the corresponding CDN or edge CNAME URL.

Sample CDN URL:

Sample direct request:

Checklist:

Request the asset directly from the origin server.

• 2xx: Please contact customer support.
• 404 Not Found: Use a SFTP client to verify that the asset can be found at the requested location.