The biggest undocumented features of the edge cache we've had to deal with is that it does not honor the Vary header, and that it is turned on when you enable billing for an app.
I agree, however, that regardless of what details are posted in this group, the edge cache behavior should be documented in the official docs. -Mike -=- On Dec 17, 9:31 am, "Ikai Lan (Google)" <[email protected]> wrote: > App Engine's edge cache is not guaranteed. It's "best effort" caching, > caching that any ISP downstream could also have implemented. > > What you'd do is set the cache-control headers to "public" and set a > max-age, and App Engine's edge caches may cache your content. There's also > no way to flush your content, but the cache is key off the URL, so use a > cache buster. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/appengine > Twitter:http://twitter.com/app_engine > > > > > > > > On Fri, Dec 17, 2010 at 9:28 AM, Matt H <[email protected]> wrote: > > This would be nice to have. > > > -- > > 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]<google-appengine%2Bunsubscrib > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- 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.
