Home/ Questions/Q 7540863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T07:44:38+00:00

I check the headers on my production server as curl –head -H Accept-Encoding: gzip

  • 0

I check the headers on my production server as

    curl --head -H "Accept-Encoding: gzip" http://foo.heroku.com/assets/mobile.js

and I get back the following headers which suggest RAILS is not setting the cachecontrol headers. 

HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Wed, 22 Jun 2011 12:01:55 GMT
Content-Type: application/javascript
Connection: keep-alive
Content-Md5: efb90436a465f8a73efb467109f745f3
Cache-Control: no-cache
Last-Modified: Wed, 22 Jun 2011 11:46:04 GMT
Etag: "efb90436a465f8a73efb467109f745f3"
X-Ua-Compatible: IE=Edge,chrome=1
X-Runtime: 0.001258
X-Content-Digest: 6493f457e9550773761bb1c2c52ec4cb44a19c19
X-Rack-Cache: stale, valid, store
X-Varnish: 164373614
Age: 0
Via: 1.1 varnish
Content-Encoding: gzip

I’d like to get heroku’s varnish cache caching the assets and only refreshing on git push. Any ideas on how to get this?

Brad

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have to add this in your environment/production.rb:

    config.serve_static_assets = true
config.static_cache_control = "public, max-age=172800"
    • 0