Last updated on: 2016-06-02
Authored by: Rackspace Support
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.
Benefits include fast load times when serving your content, access control, and origin protection. For detailed information, see Features of Rackspace CDN.
When you use Rackspace CDN, you have access to over 230 edge nodes (servers) around the world.
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.
Many web browser plugins and tools are available. For example:
Additionally, some customers use YSlow or Pingdom.
No. Rackspace CDN does not prepopulate the edge nodes. Content is copied to the edge nodes only when it is requested.
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.
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.
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.
Rackspace CDN currently has the following limits:
Yes. It is located at Rackspace CDN SLA.
Yes. See Rackspace CDN secure delivery options.
No. You are charged for storage on your origin server, but Rackspace CDN does not charge for edge node storage on top of that.
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.
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
SNI is supported for requests to the configured origin.
Yes, customers who use the shared Rackspace domain will not be charged any certificate fees.
Customers need to submit a ticket from the Control Panel with their domain details and Rackspace Support will reach out to them.
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.
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License