search

iron-io / issues

For Iron.io services issue tracking. Public facing issue tracking for behind the scenes issues.
5 stars 0 forks source link

www.iron.io assets are not cached #7

Open odeits opened 12 years ago

odeits commented 12 years ago

Static resources such as images and script files have their cache control set to no-cache. These assets should be served from a CDN and have long expire times.

treeder commented 12 years ago

Good call, we'll be working on this. Starting with changing expiry times. cc @thousandsofthem

thousandsofthem commented 12 years ago 
config.static_cache_control = "public, max-age=3600"

should help as temporary solution. we must use truly unique file names to achieve longer expire times, e.g. 1 year

odeits commented 12 years ago

Possibly helpful resources:

  1. http://code.dblock.org/rails-s3-cloudfront-jammit-heroku-100
  2. http://code.dblock.org/pushing-assets-to-s3-w-rake-versioning-and-cache-expiration