I use query strings, I append the app version number to each static resource so that caching get invalidated automatically every time I deploy a new version.
On Tuesday, 7 August 2012 20:56:53 UTC+12, prem 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/-/b2muyGhzfnQJ. 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.
