Hi Barry, You're right, it's must be a feature to avoid AppEngine "admin" headers being cached by proxies, should have thought about it by myself :-)
Thanx a lot for helping. François On Monday, January 27, 2014 3:30:45 PM UTC+1, barryhunter wrote: > > >> >> Connected with an "admin" account, caching seems to be disabled, at least >> on Chrome and Firefox. >> > > I've seen this too. > > I believe its a 'feature' - ie so the admin shouldnt see stale pages. To > make it easier to edit pages in CMS's etc. > > But it might also be to help ensure that your 'secret' information > in X-AppEngine-Estimated-CPM-US-Dollars header etc, is not accidently > cached in proxy servers. > > > > btw, a nice tool for checking caching headers is redbot.org > > > http://redbot.org/?uri=http%3A%2F%2Fdev.pronocities.com%2Ftheme%2Fcom.pronocities.theme.base%2F858%2Flogo_mail.png > > it highlights that your eTag, and if-modified-since checks (which I dont > think are implemented by the edge-cache) might not be completely > functional. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
