Hello, my case is that I have data that is fine if it's stale for some people, but I would of course not want everybody to have equally stale data.
This becomes a problem however, for of course I use the appointed HTTP caching headers per RFC 2616, section 13. To cut it briefly, I always set the expiry to tomorrow 00:00 because this is an acceptable trade- off for our purposes. When we rolled this out, everybody would be getting stale data however! It seemed the Google Frontend servers simply did not revalidate, and why should they? After all, the headers are saying it's OK until tomorrow. So basically I *do want* this behavior, but I *do not want* it for the scope that a reverse proxy provides - Google's got me by the balls here, pretty much. How do I tell the GFE not to be a reverse caching proxy? Sincerely -Ludvig Ericson, http://sendapatch.se/ -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
