Deliver content over HTTP through the following procedure:
-
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.
- Configure your firewall to allow our network to communicate with your web servers.
- 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.
- 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.
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 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.
Load the Customer Origin Page
A customer origin configuration allows the CDN to serve traffic.
Navigate to the Customer Origin page. 
How?
The Customer Origin page will immediately show a blank customer origin configuration.
IP Preference
By default, our CDN service will resolve hostnames to IPv4.
Directory Name
Assign a unique name to a customer origin configuration. This name will be incorporated into the 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. generated for this customer origin.
Sample CDN URL for a customer origin called "marketing":
In the Directory Name option, type an alphanumeric word or phrase (e.g., marketing).
The CDN service must be informed where to find each web server associated with this customer origin configuration. This step involves providing one or more IP addresses or hostnames that point to your web servers.
Make sure that the HTTP Edge Protocol option is marked.
In the Hostname or IP Address option, type the hostname or IP address of the server where your data resides. Append a colon and the port through which communication will take place (e.g., http://marketing.mydomain.com:80).
Click Add which appears directly to the right of the Hostname or IP Address option.
Configuring CAN Gateway Servers
A CAN Gateway server optimizes the communication path between the edge of our network and your web servers (i.e., customer origin servers). Setting up CAN Gateway servers requires testing connectivity between each CAN Gateway server and the servers associated with the customer origin configuration (as defined in the Web Server Information step).
Upload a 5 KB asset to each web server associated with this customer origin configuration.
Multiple Servers: Make sure to upload this sample asset to the same location on each web server.
In the Validation Path option, type a URL that points to the asset uploaded in the previous step. Make sure that the hostname specified in this URL matches the value defined in the HTTP Host Header option.
Click Validate. If the result returns 200 OK for all hostnames/IP addresses, then proceed to the next step.
Create the customer origin configuration by saving your changes.
Click Add to save your customer origin configuration.
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 within the Whitelist IP Blocks section of the Customer Origin 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.
View an alternative approach.
An alternative method for serving traffic is to update all links to use the CDN URL generated for the recently created customer origin configuration. This CDN URL is listed under the Full URL column.
It may take up to an hour after the creation of a customer origin configuration before it may serve traffic.
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. points to the root virtual directory for the web servers defined in the customer origin configuration.
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. How?
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.
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.
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.
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., cdn1.mydomain.com).
Update the CNAME's value to resolve to the CDN hostname copied above.
Once this DNS change takes effect, traffic will shift to our CDN service.
More Information
Edgecast CDN