After researching this for the original poster on stackoverflow, I am seeing the same thing with my own custom domains.
When hitting a route that has public caching setup - the edge cache doesn't work when hitting that url from the custom domain. It always returns 200 status in app engine logs. However, hitting that same app engine app via APP_ID.appspot.com domain - it starts taking advantage of the edge cache almost immediately. In that case it returns 204 status as expected. Sample snippet to get these pages to publicly cache is: response.headers['Pragma'] = 'Public' response.headers['Cache-Control'] = 'public, max-age=%d'%time The edge cache used to work when routing through a domain but doesn't seem to any more. Jeff On Thursday, July 16, 2015 at 11:53:43 AM UTC-5, Lucemia wrote: > > By my experiment in these days, it looks like google appengine edge cache > not work for custom domain (app domain) recently ( or change its rules). > However, for *.appspot.com, the edge cache worked as before. > > Any one has the same issues? Is it a rule changes / temp bugs ? > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/048a02da-9662-48bd-bd6d-64d13628271b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
