Linking to Content Tutorials

The recommended approach to switching traffic over to our CDN service is to update a CNAME recordA Canonical Name (CNAME) record is used to indicate that a hostname is an alias of another hostname. A CNAME record must be registered on a Domain Name System (DNS). This term should not be confused with edge CNAME. via your DNS service provider. This approach is described in the following tutorials:

Alternatively, you will need to update all of your links to use a 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. or 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.. This topic contains tutorials that explain how to:

Constructing a CDN URL for your Web Servers Tutorial

The following information is required to manually construct a CDN URL:

If you haven't already created a customer origin configuration, then please do so before continuing.

Choose a Delivery Platform

Accelerate HTTP traffic by serving it through one or more of the following platforms:

Based on the following questions, choose the first platform that fits your traffic profile.

  1. Do you plan on serving content that varies by user?

    This type of content is typically generated using a scripting language (e.g., PHP).

    If so, use 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..

  2. Does most of your content consist of static content? Static content are files stored on disk, such as HTML, CSS, JavaScript, high resolution images, multimedia, and software downloads.

    If so, use 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..

Select a Base URL

Selecting a base URL requires choosing the CDN URL that corresponds to the desired customer origin.

Navigate to the home page of the desired platform. ClosedHow?From the main menu, navigate to [HTTP Large, HTTP Small, or ADN]

Under the URLs for your Origin section, look for the CDN URL corresponding to the previously created customer origin.

Syntax:

Sample Base CDN URL (Customer Origin):

http://adn.0001.edgecastcdn.net/800001/marketing

Append a URL Path

A base CDN URL for a customer origin configuration points to your web server's root folder/virtual directory. If your site points to the same virtual directory, then you can construct a CDN URL by appending to it a URL pathRefers to the portion of the URL that appears directly after the hostname. It provides the relative path to a specific folder or asset. that points to the desired asset.

Append the desired URL path to the base CDN URL.

Sample Scenario

This example will construct a URL from the following base CDN URL:

http://adn.0001.edgecastcdn.net/800001/marketing

Let's assume that the above base CDN URL is equivalent to the following URL:

http://www.mydomain.com

Let's assume that you are trying to construct a CDN URL that points to the following image file (i.e., flyer01.png).

http://www.mydomain.com/ad/campaign/snow/flyer01.png

Append the above URL path, as indicated in blue font, to the base CDN URL. This should result in the following CDN URL:

http://adn.0001.edgecastcdn.net/800001/marketing/ad/campaign/snow/flyer01.png

Constructing an Edge CNAME URL for your Web Servers Tutorial

The following information is required to manually construct an edge CNAME URL:

If you haven't already created a customer origin and an edge CNAME configuration, then please do so before continuing.

Choose a Delivery Platform

Accelerate HTTP traffic by serving it through one or more of the following platforms:

Based on the following questions, choose the first platform that fits your traffic profile.

  1. Do you plan on serving content that varies by user?

    This type of content is typically generated using a scripting language (e.g., PHP).

    If so, use 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..

  2. Does most of your content consist of static content? Static content are files stored on disk, such as HTML, CSS, JavaScript, high resolution images, multimedia, and software downloads.

    If so, use 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..

Select a Base URL

Selecting a base URL requires choosing an edge CNAME URL that corresponds to the desired customer origin.

Navigate to the home page of the desired platform. ClosedHow?From the main menu, navigate to [HTTP Large, HTTP Small, or ADN]

Under the URLs for your Origin section, look for the edge CNAME URL that points to the desired web servers.

A list of hostnames or IP addresses to which the CDN will resolve requests is provided directly to the right of each URL.

Sample Base Edge CNAME URL:

http://cdn1.mydomain.com

Append a URL Path

By default, a base edge CNAME URL for a customer origin configuration points to your web server's root folder/virtual directory. This allows an edge CNAME URL to be constructed by appending a URL pathRefers to the portion of the URL that appears directly after the hostname. It provides the relative path to a specific folder or asset. that points to the desired asset.

A relative path may be assigned to an edge CNAME configuration. This configures the base edge CNAME URL to point to the subdirectory identified by that relative path.

Append the desired URL path to the base edge CNAME URL.

Sample Scenario 1: Virtual Directory

This example will construct a URL from the following base edge CNAME URL:

http://cdn.mydomain.com

Let's assume that the above edge CNAME URL is the equivalent to the following base URL:

http://www.mydomain.com

Let's assume that you are trying to construct a edge CNAME URL that points to the following image file (i.e., flyer01.png).

http://www.mydomain.com/ad/campaign/snow/flyer01.png

Append the above URL path, as indicated in blue font, to the base edge CNAME URL. This should result in the following edge CNAME URL:

http://cdn.mydomain.com/ad/campaign/snow/flyer01.png

Sample Scenario 2: Relative Path

This second scenario builds off the above sample scenario. However, in this scenario, the edge CNAME configuration has been modified to point to the following relative path:

As a result of this configuration, the base edge CNAME URL now points to the following CDN URL:

http://adn.0001.edgecastcdn.net/800001/marketing/ad/campaign

Additionally, the above CDN URL is now equivalent to the following URL:

http://www.mydomain.com/ad/campaign

Let's assume that you are trying to construct an edge CNAME URL that points to the following image file (i.e., flyer01.png).

http://www.mydomain.com/ad/campaign/snow/flyer01.png

Append the above relative path, as indicated in blue font, to the base edge CNAME URL. This should result in the following edge CNAME URL:

http://cdn.mydomain.com/snow/flyer01.png
More Information