The Google App Engine must have some kind of reverse caching proxy, because when I set the Cache-Control public, max-age=300 response header Cache-Control public, max-age=300 from one of my servlets, subsequent requests to the application engine appear in the logs as follows: /testcaching 204 1ms 0cpu_ms 49kb , while non-cached appear in the logs as: /testcaching 200 61ms 77cpu_ms 49kb .
Anyway, my question is: are there any details about this reverse caching proxy?
google-app-engine caching
Kyle Oct. 16 '10 at 4:12 2010-10-16 04:12
source share