0 down vote favorite
I notice that in my production enviornment (where I have memcached
implemented) in see a cache-control - max-age header in firebug,
anytime I am looking at an index page (posts for example).
In my dev environment that header looks like following.
Cache-Contro private, max-age=0, must-revalidate
As far as I know I have not done anything special with my nginx.conf
file to specify max age for regular content, I do have expires-max set
for css, jpg etc. here is my nginx.conf file..
So why is this cache-control is being set? How can I control this
cache-control, because the side effect of this is kinda bad. This is
1 - User request all_posts listing and get a list of 10 pages
2 - User view page 1, 2 3 and the respective caches are created.
3 - User goes back to page 1 and firefox does not even make a request
to the server. Normally I would expect it would reqeust and hit the
cache created in step #2.
The other issue is that if a new post has been created and now the
cache is refreshed and it should be at the top of page 1, the user
does not get to see it..because the browser isn't hitting the server.
I tried setting expires_now in my index action. NO difference the max-
age is still the same large value.