When HTTP cache headers are set, the documents can be cached on these network resources, and client requests can be satisfied without having to go back to the origin server.
设置了http缓存表题头之后，可以在这些网络资源上对文档进行缓存，客户端请求也可在不必返回原始服务器的情况下得以满足。
Besides the fine tuning you can do with cache headers, this service also gzips files returned to the client, if the client is capable of receiving and processing gzip content.
除了对缓存头文件执行微调优，该服务还压缩返回给客户的的文件，如果客户端能够接收和处理gzip内容的话。
For example, by setting certain caching headers in your data services, you can use the browser as a free cache.
例如，通过在您的数据服务中设置某个缓存消息头，您可以将浏览器作为一个自由缓存使用。
Pause 20 seconds between requests; you should see an obvious cache miss because this content has expired per its outgoing headers.
在请求之间暂停20秒；您应当会看到明显的缓存丢失，因为根据它的传出报头，此内容已过期。
Also, to make a resource request cacheable, you need to explicitly set the cache control information on the response so that the portal can generate caching headers.
此外，要使资源请求可缓存，您需要在响应上显式设置缓存控制信息，以便门户能够生成缓存标头。
You can reduce HTTP requests by providing HTTP cache expiration headers with future dates that allow browsers to cache components.
可以提供指定了未来日期的HTTP缓存过期头，这会让浏览器对组件进行缓存，因此可以减少HTTP请求。
You can even drill into requests to see the HTTP headers sent, the response received, and the relevant cache information for the file in question.
还可以深入这些请求，查看发送的HTTP头部、接收到的响应、所用文件相关缓存信息。
Proxies can also cache frequently loaded content if proper expiration headers are provided. An expiration header looks like this
如果提供了适当的过期头，代理也可以缓存经常装载的内容。
You should aggressively cache files using Expires or Cache-Control headers.
并且要使用Expires或者Cache - Controlheader来主动缓冲文件。
To watch the HTTP headers in action, let's build, install, and run an HTTP reverse proxy to cache the output of a small PHP application.
要查看HTTP报头如何工作，让我们构建、安装并运行一个HTTP反向代理来缓存一个小型PHP应用程序的输出。
If the response’s headers tell the cache not to keep it, it won’t.
如果响应头信息：告诉缓存器不要保留缓存，缓存器就不会缓存相应内容；
After that time, caches will always check back with the origin server to see if a document is changed. Expires headers are supported by practically every cache.
过了这个时间，缓存器就会向源服务器发送请求，检查文档是否被修改。
Despite their names, neither a 301 nor a 302 response is cached in practice unless additional headers, such as Expires or Cache-Control, indicate it should be.
尽管他们的名字既不一的 301，也不 302响应缓存在实践除非附加的标头如过期或Cache-Control显示它应该是。
A typical web browser will cache a file for a fixed amount of time, as directed by the Cache-Control or Expires headers in the server response.
典型的Web浏览器会在一定时间内缓存某个文件，如服务器响应中的Cache -Control或expires头文件所示。
The tests included individual cache limits and support for Last-Modified and ETag page headers, and for whether the cache was preserved after turning the device off and back on.
测试包括缓存限制、对网页更新判断和ETag的支持，以及重启后缓存是否保留。
Two other headers are used in tandem with Cache-Control to control retention.
另外两个报头将与Cache - Control结合使用来控制保持力。
To use Cache-Control headers, choose Content Management | Cache Control Directives in the administration server.
使用Cache-Control头信息，在管理服务器上选择内容管理|缓存设置目录。
HTTP 1.1 introduced a new class of headers, Cache-Control response headers, to give Web publishers more control over their content, and to address the limitations of Expires.
HTTP 1.1介绍了另外一组头信息属性：Cache -Control响应头信息，让网站的发布者可以更全面的控制他们的内容，并定位过期时间的限制。
Useful Cache-Control response headers include
有用的Cache-Control响应头信息包括
The web server should serve the manifest file with no-cache response headers.
web服务器应当在不带缓存响应头的情况下为清单文件提供服务。
When the edge server receives the response from the origin server, it stores the content in cache based on the HTTP headers of the response.
当边缘服务器接收从到源服务器的内容，它将基于响应内容中的HTTP头建立内容的缓存。
Entities on the Web that cache Web pages cache multiple versions, based on the HTTP headers and other factors.
可缓存网页的网站上的实体可基于HTTP标头和其他因素缓存多个版本。
It includes the HTTP headers from the original client request so that the cache server may process them, if necessary, as part of the request.
它包括原始客户机请求的HTTP标头，以便高速缓存服务器能够在必须时将它们作为请求的一部分来处理。
It includes the HTTP headers from the original client request so that the cache server may process them, if necessary, as part of the request.
它包括原始客户机请求的HTTP标头，以便高速缓存服务器能够在必须时将它们作为请求的一部分来处理。
应用推荐