Hi Joshua, The edge cache is just that - a cache. It doesn't guarantee that no 304 requests will reach your app, only that they will be satisfied by the cache if possible - and if the headers you set permit it. The more popular your content is, the more effect you're likely to see from the cache.
-Nick Johnson On Fri, Sep 16, 2011 at 1:26 PM, Joshua Bronson <jabron...@gmail.com> wrote: > Hey GAE devs, > > We just enabled billing for our app, but contrary to past > reports<https://groups.google.com/d/topic/google-appengine/8QgEUBOiNFw/discussion>, > 304 responses are still being served by our Python code rather than by GAE's > edge cache, whether requested via our appspot domain or our Google Apps > domain. > > Was the edge cache disabled for non-static resources since last report? Any > info you could provide on the status of the edge cache would be super > helpful. > > Thanks. > > -- > 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/-/2kmTyfznZmEJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Nick Johnson, Developer Programs Engineer, App Engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
