Hi craayzie person, You may want to take a look at http://redbot.org/
It tends to give some good pointers to debugging cache headers. You may also want to implement some server side behavior to leverage the ETag Also check out http://railslab.newrelic.com/2009/02/26/episode-11-advanced-http-caching There are lots of great articles there, but that one in particular may shed some light. --Keenan On Tuesday, May 31, 2011 at 8:25 PM, craayzie wrote: > I'm setting a 'Cache-Control: public, max-age=300' response header per > the Heroku docs but when I request the resource, Heroku logs show my > app processing the request and subsequent requests for the same > resource continue to hit my app. > > Any guidance on how to troubleshoot this further to figure out why > Varnish isn't caching? > > Here are the response headers from Heroku: > > < HTTP/1.1 200 OK > < Server: nginx/0.7.67 > < Date: Wed, 01 Jun 2011 00:24:28 GMT > < Content-Type: text/html; charset=utf-8 > < Connection: keep-alive > < ETag: "8b8a779a2522e7a42fc663b76a088763" > < X-UA-Compatible: IE=Edge,chrome=1 > < X-Runtime: 0.047719 > < Cache-Control: public, max-age=300 > < Content-Length: 6921 > < X-Varnish: 1131028875 > < Age: 0 > < Via: 1.1 varnish > > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com > (mailto:heroku@googlegroups.com). > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > (mailto:heroku+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
