Delivering Content over HTTP Tutorial

Deliver content over HTTP through the following procedure:

  1. Choose a delivery platform.
  2. Configure the CDN to communicate with your web servers by creating a customer originRefers to a CDN configuration that identifies one or more web servers that will serve as the source from which content may be delivered via the CDN. configuration.

    Alternatively, content may be served from our CDN storage solution or an Azure block blob container.

  3. Configure your firewall to allow our network to communicate with your web servers.
  4. Prepare the CDN to route traffic to your web servers by creating an edge CNAMERefers to the mapping of a CNAME record to a directory on a CDN or customer origin server. The purpose of this mapping, which is only used by our CDN, is to establish a user-friendly alias for content served through the CDN. It relies upon your CNAME record being mapped to a CDN hostname via a DNS service provider. configuration.
  5. Switch traffic to our service by updating 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.

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

Configure the CDN to Communicate with your Web Servers

Before the CDN may serve traffic from your web servers, it must be informed where they are located via a platform-specific customer originRefers to a CDN configuration that identifies one or more web servers that will serve as the source from which content may be delivered via the CDN. configuration.

Create either a customer origin group.

Set up Firewall Access

The next step is to ensure that a firewall doesn't block the flow of traffic between your web servers and the CDN.

Configure your firewall to allow all of our IP blocks access to your server(s).

View our IP blocks by navigating to the Whitelist IP Blocks page.

Serve Traffic

The recommended approach for serving traffic is to leverage a CNAME record for use with our CDN service. Continue to the next section to learn more.

Create an Edge CNAME Configuration

Create an edge CNAME configuration that will direct traffic to a customer origin configuration. This friendlier URL allows traffic to be shifted to the CDN by simply updating a CNAME record to point to a CDN hostnameRefers to a system-defined hostname that is specific to your customer account and a CDN service..

Navigate to Edge CNAME Settings

An edge CNAME configuration must be created on the same platform as the customer origin that was created earlier in this tutorial.

Navigate to the Edge CNAMEs page corresponding to the platform to which the desired customer origin was added. ClosedHow?From the main menu, navigate to [HTTP Large, HTTP Small, or ADN] | Edge CNAMEs.

Name an Edge CNAME

An edge CNAME configuration should be named after the hostname defined in the desired CNAME record.

This name should be specified in lower-case letters and should not include a protocol (e.g., http://).

In the New Edge Cname option, type the hostname through which traffic will be served.

New Edge CNAME Option - Edge CNAME Configuration

Identify a Customer Origin

This step defines the customer origin from which requests to this edge CNAME will be served.

In the Points to option, verify that "Customer Origin" is selected.

In the Origin Directory option, select the recently created customer origin configuration.

Defining the Origin Server

Save Changes

Create an edge CNAME by saving your changes.

Click Add.

An edge CNAME that points to a customer origin configuration should appear at the top of the Edge CNAMEs page.

New Edge CNAME

Wait an hour to allow your changes to be applied before proceeding beyond this point.

Update a CNAME Record via a DNS Service Provider

Switching traffic over to our CDN service requires updating a CNAME record to point to an edge CNAME .

From the Edge CNAMEs page, copy the hostname defined under the Points To column.

Load your DNS service provider's portal.

Find the CNAME record corresponding to the edge CNAME created above (e.g.,

Update the CNAME's value to resolve to the CDN hostname copied above.

Your DNS service provider should provide settings similar to those shown below.

Once this DNS change takes effect, traffic will shift to our CDN service.

More Information