"Cache-Control: private" only uses the end user cache to cache resources.
"Cache-Control: public" uses any downstream cache to cache resources (including the browser cache). Google has a downstream cache in front of App Engine requests, so if you serve your resources with "Cache-Control: public", Google will cache that resource. Subsequent hits are served from there, and I'm pretty sure they won't even show in your request log at all. j On Dec 6, 3:19 pm, GONZO <gonzom...@gmail.com> wrote: > Hi, first thanks for your attention and sorry for my English > translation. > > I have a question that intrigues me a few weeks. This is the header > "cache-control" in particular the behavior of the options "private" > and "public" in Google App Engine. > > First of all, this is only to serve static files (css, js, etc) > > Let's go. With "cache-control: private" experiment curve normal > traffic. But with "cache-control: public" experiment Traffic > incredible savings. In both cases, everything seems to work well. > > The question is: > > 1. How can traffic be a big savings? Is reduced to 15%. > > 2. Saving you a real traffic? Or is something special instead of > Google App Engine? > > Better look at this diagram > illustrates:http://gonzo.teoriza.com/almacen/cache-control.jpg > > Thanks in advance, I hope to be clarified. -- 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-appeng...@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.
