TTL or Far Future Expiration
I can only set the max TTL to 72 hours on RSC Files. Is there any way for me to add the far future expires headers to a month at least?
We extended the TTL in March of 2011. See our blog for more details…
Kelly Haywood commented
Since it's still not in the control panel anyone viewing this post should check out http://www.bybe.net/blog/how-to-fix-rackspace-file-cloud-leverage-browser-caching-via-api-ssh.html
You can set longer TTL's usings using your Rackspace Server Cloud SSH along with CURL installed.
Cloud Files support setting the TTL from 15 seconds to 50 years.
Rex Morgan commented
This seems like a no-brainer, since the whole point of a CDN is for people to be able to download your files as quickly as possible. What's faster than not having to download them at all? I decided to give cloud files a pass on CNAMES, since it was really just aesthetics, but this is pretty crucial.
Disappointed with this one.
Would also vote all 15 votes if I could
When I could, I would have given this all 15 points. Lack of a long TTL is a show stopper: not using Rackspace CDN service.
The maximum TTL of 72 hours is below Google's Page Speed add-on recommended value.
Quote #1: Cacheable resources shouldn't have a short freshness lifetime. Specify an expiration at least one week (= 168 hours) in the future.
Quote #2: Set Expires to a minimum of one month, and preferably up to one year, in the future.
1 year at most please.