Rackspace CDN FAQ

Get quick answers to common questions about the Rackspace CDN service. If you have any questions about the terms used in this FAQ, see the Rackspace CDN terminology page.

Getting Started

How does Rackspace CDN benefit my website or web application?

Benefits include fast load times when serving your content, access control, and origin protection. For detailed information, see Features of Rackspace CDN.

How many edge servers does Rackspace CDN give me access to?

When you use Rackspace CDN, you have access to over 230 edge nodes (servers) around the world.

Can I specify certain files for caching or create specific inclusions and exclusions?

Yes, you can set a time to live (TTL) of 0 on any content that you don’t want served from an edge node. You might choose to do this for dynamic content that changes for every visitor.

How can I check the performance of my site?

Many web browser plugins and tools are available. For example:

  • In Firefox, click Tools > Web Developer > Network. If you don’t see the Tools menu, press the F10 key on your keyboard.
  • In Chrome, you can use the Page load time plugin

Additionally, some customers use YSlow or Pingdom.

Can I push content to edge nodes before it’s needed?

No. Rackspace CDN does not prepopulate the edge nodes. Content is copied to the edge nodes only when it is requested.

How does origin pull work?

Rackspace CDN seamlessly and automatically fetches content from an origin server and caches it at the edge location if the edge location doesn’t already have it.

Can content be pulled from anywhere, including sources external to Rackspace?

Yes. Rackspace CDN can pull content from any origin with a public IP address or web address, including servers hosted in our public, private, or dedicated infrastructures, as well as servers hosted offsite.

What are my options for serving traffic over HTTPS?

Rackspace CDN works with shared domain SSL, SSL SAN certificates, and fully owned certificates. Our custom SSL options satisfy your security, budget, and marketing requirements. Pricing for each option is different.

What are the limits of Rackspace CDN?

Rackspace CDN currently has the following limits:

  • 10 domains per service
  • 8 KB maximum size for request body in the API

General

Is there a service level agreement (SLA) for Rackspace CDN?

Yes. It is located at Rackspace CDN SLA.

Can you provide pricing information for Rackspace CDN?

See Rackspace CDN pricing.

Is there a list of approved Certificate Authorities (CAs) for Rackspace CDN?

Yes. See Rackspace CDN secure delivery options.

Will I be charged for edge node storage when I use Rackspace CDN?

No. You are charged for storage on your origin server, but Rackspace CDN does not charge for edge node storage on top of that.

Does Rackspace CDN honor the Expires header value set by the origin server (web server)?

If the content is cacheable and you have not set a time to live (TTL) rule on the service, edge nodes honor the Expires or Cache Control headers sent by the origin server. When a request is made to the origin for content, the edge node looks for Expires or Cache Control headers in the response sent by the origin. If these headers are present, the TTL for that content matches the time referenced in the Expires or Cache Control headers. If both Expires and Cache Control headers are present, Cache Control takes precedence.

If the content is cacheable and you have set a TTL on the service, the caching TTL is honored. The Cache Control and Expires headers are ignored, and content is refreshed based on the TTL value that you set. This rule applies only to content that matches the path specified in the TTL rule. For example, if you have a TTL rule for the page /images/*, then all Expires and Cache Control headers for content that is not in the images directory is honored.

If the content is not cacheable, it is not cached on the edge nodes, regardless of the origin headers.

Note: A default caching rule with a TTL of 1 day and a request_url of /* is set for all content. You need to remove your default caching in order to hone origin headers.

What is cacheable content?

Content with the following file extensions is cacheable:

aif, aiff, au, avi, bin, bmp, cab, carb, cct, cdf, class, css, doc, dcr, dtd, exe, flv, gcf, gff, gif, grv, hdml, hqx, ico, ini, jpeg, jpg, js, mov, mp3, nc, pct, pdf, png, ppc, pws, swa, swf, txt, vbs, w32, wav, wbmp, wml, wmlc, wmls, wmlsc, xsd, zip, webp, jxr, hdp, wdp

Does Rackspace CDN support Server Name Indication (SNI)?

SNI is supported for requests to the configured origin.

Does Rackspace CDN have a free secure delivery option?

Yes, customers who use the shared Rackspace domain will not be charged any certificate fees.

What is the process for requesting a dedicated certificate?

Customers need to submit a ticket from the Control Panel with their domain details and Rackspace Support will reach out to them.

What should customers expect after they provision a certificate?

The administrator for the domain will be contacted by Symantec and/or Digicert to verify the domain. It is critical that customers respond to this verification request. Certificates will not be provisioned until it is complete.