[google-appengine] Incredible traffic saving with the header "Cache-control: public"???
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.
[google-appengine] Re: Incredible traffic saving with the header "Cache-control: public"???
Hi, thanks for your response. I like your answer. Just what I expected. Confirms my theory and my experiences. I confirm that requests saved (90%) do not appear in the logs and not counted in the consumption of bandwidth. It's free total. Amazing. I appreciate all the information you know about it. Thank you all. Greetings! On 8 dic, 03:51, Jason Collins wrote: > "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 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.
[google-appengine] Re: Incredible traffic saving with the header "Cache-control: public"???
Quizás quisiste decir: A mi no me aparece esto. Puede garantizar que la diferencia entre cache-control private y public es que con public Escribe texto o la dirección de un sitio web o traduce un documento. Cancelar Escuchar traducción del español al inglés I do not look like this. I can guarantee that the cache-control difference between private and public is that public away 95% of traffic, almost all. However, this is served 100% ok to customers. The traffic is not on any chart, or if the consumption of bandwidth or in the logs. On 15 dic, 03:29, Albert wrote: > Hi! > > This guy seems to implement something similar to yours, but he says, > "...each time a page is served cached, you'll see a 204 logged in your > Appengine dashboard." > > http://www.kyle-jensen.com/proxy-caching-on-google-appengine > > Did any of you guys notice that too? > > Albert > > On Dec 15, 9:29 am, GONZO wrote: > > > Hi, thanks for your response. > > > I like your answer. Just what I expected. Confirms my theory and my > > experiences. > > > I confirm that requests saved (90%) do not appear in the logs and not > > counted in the consumption of bandwidth. It's free total. Amazing. > > > I appreciate all the information you know about it. > > > Thank you all. Greetings! > > > On 8 dic, 03:51, Jason Collins wrote: > > > > "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 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.
