I'm seeing the same behavior as craayzie. Redbot shows headers that
look correct:
HTTP/1.1 200 OK
Server: nginx/0.7.67
Date: Wed, 01 Jun 2011 20:16:01 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Last-Modified: Wed, 11 May 2011 19:35:02 GMT
Cache-Control: max-age=86400, public
X-UA-Compatible: IE=Edge,chrome=1
X-Runtime: 0.006309
Content-Length: 403
X-Varnish: 1696646971
Age: 0
Via: 1.1 varnish
If I point Redbot to the same url repeatedly, it shows the same
headers every time, but the logs show that each request is hitting my
rails app. Varnish isn't serving it for some reason.
I'm on Bamboo, so Varnish should be working, it's just... not. This
app is only at one dyno currently.
On May 31, 5:25 pm, craayzie <[email protected]> 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 [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.
