According to the dev centre anything server from the file system (a Rack::File) on the Aspen and Bamboo stacks is cached for 12 hours.
Does anyone know how Heroku handles the new assets pipeline in Rails 3.1? Wondering if everything from /assets is being cached in the same way, so far it appears not. I'm getting Cache-Control no-cache on all images being served from /assets in our 3.1 app. 1. Cache-Control: no-cache 2. Connection: close 3. Date: Thu, 07 Jul 2011 10:57:05 GMT 4. Etag: "85a0a88982a5cca265f971c34d49b036" 5. Last-Modified: Tue, 05 Jul 2011 08:34:57 GMT 6. Server: nginx/0.7.67 7. Via: 1.1 varnish 8. X-Varnish: 1701811975 Stylesheets and scripts from the same directory are being cached however: 1. Age: 171642 2. Cache-Control: public, max-age=31536000 3. Connection: close 4. Content-Encoding: gzip 5. Content-Md5: e1a3a8499f08caa743f57876c5983118 6. Content-Type: text/css 7. Date: Thu, 07 Jul 2011 08:32:36 GMT 8. Etag: "e1a3a8499f08caa743f57876c5983118" 9. Last-Modified: Tue, 05 Jul 2011 08:34:57 GMT 10. Server: nginx/0.7.67 11. Transfer-Encoding: Identity 12. Via: 1.1 varnish 13. X-Content-Digest: 4b73f049b043579fd9de0c9258dc1ee74da2c8bd 14. X-Rack-Cache: fresh 15. X-Runtime: 0.001918 16. X-Ua-Compatible: IE=Edge,chrome=1 17. X-Varnish: 636946648 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/_6GOepq4SEcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
