Basic Setup

Before you can start delivering data to your clients, you will need to do the following:

Decide the source for your content (e.g., external web server(s) or CDN storage).

Learn more.

Serving traffic via our CDN requires one or more web servers that contain your content. This type of server is known as an origin server, since it is the origin or source of the content that will be delivered to your users. A brief description is provided below for each type of origin server.

Origin Server Type	Description
External Web Server	Our CDN service can be configured to recognize a web server that is external to our network (e.g., web hosting). The main advantages of using an external web server are: Minimal Setup: Setting up an external web server is as simple as creating a customer origin configuration from within the TCC. All of your data can remain as it is currently structured on your web server. This saves you the amount of time it takes to upload and maintain that data on a separate server. Create an edge CNAME configuration and then update your DNS configuration to quickly shift traffic to our CDN service. View tutorial. Response Headers: Our edge servers will forward the majority of response headers provided by your web server to your users. A benefit from this behavior is that you can define the cache instructions that will be assigned to assets served from your web server(s) without having to define a custom rule via Rules Engine.
CDN Origin Server	Our standard CDN storage service is designed to allow the storage and retrieval of files. Content may be: Uploaded to CDN storage via rsync, SFTP, or FTP. Delivered from CDN storage to users via any of our CDN services. CDN storage content is stored and delivered via CDN origin servers. The main benefits of using our standard CDN storage service are: Availability: Our highly distributed network provides protection against network issues due to denial of service attacks or high traffic volume. This guarantees that data remains available for delivery to your clients. Speed: Data does not have to be retrieved from a location outside our network. This allows it to fully leverage our high-speed network to deliver content faster to your clients.

Origin Server Type

Description

External Web Server

Our CDN service can be configured to recognize a web server that is external to our network (e.g., web hosting).

The main advantages of using an external web server are:

Minimal Setup: Setting up an external web server is as simple as creating a customer origin configuration from within the TCC. All of your data can remain as it is currently structured on your web server. This saves you the amount of time it takes to upload and maintain that data on a separate server.

Create an edge CNAME configuration and then update your DNS configuration to quickly shift traffic to our CDN service.
View tutorial.
Response Headers: Our edge servers will forward the majority of response headers provided by your web server to your users. A benefit from this behavior is that you can define the cache instructions that will be assigned to assets served from your web server(s) without having to define a custom rule via Rules Engine.

CDN Origin Server

Our standard CDN storage service is designed to allow the storage and retrieval of files.

Content may be:

Uploaded to CDN storage via rsync, SFTP, or FTP.
Delivered from CDN storage to users via any of our CDN services.

CDN storage content is stored and delivered via CDN origin servers.

The main benefits of using our standard CDN storage service are:

Availability: Our highly distributed network provides protection against network issues due to denial of service attacks or high traffic volume. This guarantees that data remains available for delivery to your clients.
Speed: Data does not have to be retrieved from a location outside our network. This allows it to fully leverage our high-speed network to deliver content faster to your clients.

Leverage multiple origin servers to serve traffic from various sources.

Decide how you will link to your content.
Understand how requests for your content are handled by our CDN.
Become familiar with the common HTTP status codes that may be returned to a client in response to a request.