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
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
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,
Hi Gonzo,
If you have a lot of authenticated users the difference you are seeing
is probably in the cached authenticated requests.
From http://www.mnot.net/cache_docs/:
My pages are password-protected; how do proxy caches deal with them?
By default, pages protected with HTTP authentication
yes, incredible savings. Need to include a version number or hash tag
in the URL
to ensure that new versions get pushed in sync. An example:
http://bbfdirect.com/
I'm working on the next level, which is enable cache-control for the
HTML itself,
i.e. render the page and then make AJAX
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,
