Thanks for the response but I'm still not completely sure I understand. The thing is, I don't want to set a max age because I can't really predict when the information on the page will be out of date. I want to use a conditional GET so Rails gets to decide if the page is stale or not. If it's stale it re-renders the page, if not it sends a 304 - not modified header to either Varnish or the browser, I'm not sure about that.
In other words, in this case wouldn't I want Varnish to think the page is stale and send it to Rails? On Mar 23, 3:12 pm, John McCaffrey <[email protected]> wrote: <http://redbot.org/?uri=http%3A%2F%2Fhigh-night-436.heroku.com %2Fthing...>I > see that the cache is set to private, so varnish can't cache it and the max > age and age are both 0, so the browser thinks its stale, and has to > revalidate it. -- 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.
