Hi prem, I would suggest setting appropriate cache timeout rather than trying to control every edge-cache type things, because even if you use your own edge cache system, it is possible there are other edge-cache systems between your end-users and your edge-cache.
On Tue, Aug 7, 2012 at 5:56 PM, prem <[email protected]> wrote: > > I have been learning GAE(python) for my next project, a custom multi-tenant > CMS. Everything look great, except for 1 major blocker. > > Most of content pages in the CMS usually won't change for months, so edge > caching is important. When end users edit the pages, I would need to > purge/invalidate the edge-cache. > > My understanding is, currently GAE, does not allow the edge-cache to be > purged/invalidated. > > The next option would be to use an external CDN ( MaxCDN/Cloudfare/etc) or > maybe Varnish. > > My concern is, any cache headers present in pages will be processed by GAE > edge-cache as well as external cache. > > Is it possible to prevent GAE from edge-caching even if the cache headers > are set in response pages? > > -prem > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/HYqCDuoDtE4J. > 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. -- Takashi Matsuo | Developer Advocate | [email protected] -- 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.
