有关 Google App Engine 缓存代理的详细信息? [英] Details on Google App Engine's caching proxy?

问题描述

Google App Engine 必须具有某种反向缓存代理，因为当我从我的一个 servlet 设置响应标头 Cache-Control public, max-age=300 时，对应用引擎的后续请求在日志中显示如下:/testcaching 204 1ms 0cpu_ms 49kb，而非缓存请求在日志中显示为:/testcaching 200 61ms 77cpu_ms 49kb.>

无论如何，我的问题是:有没有人有关于这个反向缓存代理的更多细节?

解决方案

有些细节很高兴得到答案:

http://code.google.com/p/googleappengine/issues/detail?id=2258#c3

Google App Engine must have some sort of reverse caching proxy because when I set the response header Cache-Control public, max-age=300 from one of my servlets, subsequent requests to the app engine show up in the logs like this: /testcaching 204 1ms 0cpu_ms 49kb, whereas non-cached requests show up in the logs as: /testcaching 200 61ms 77cpu_ms 49kb.

Anyways, my question is: Does anyone have any more details about this reverse caching proxy?

解决方案

Some of the details it would be nice to have answers for:

http://code.google.com/p/googleappengine/issues/detail?id=2258#c3

这篇关于有关 Google App Engine 缓存代理的详细信息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！