See Also: HttpCacheVaryByContentEncodings Members
The HttpCachePolicy.VaryByContentEncodings property is used to specify whether dynamically compressed responses are cached. Caching dynamically compressed responses means that the cost of compression is incurred only one time, during the first request for the resource (or after an application restart) and when the cache item expires.
The HttpCachePolicy.VaryByContentEncodings property of the System.Web.HttpCachePolicy class identifies which request header parameters ASP.NET uses to uniquely identify a variation of the response if there are multiple cached responses for a resource. This is useful when a response depends on a set of client inputs, such as headers, parameters, or content encodings.
The System.Web.HttpCacheVaryByContentEncodings class is not directly related to HTTP cache-control headers. However, it helps make sure that a response to a client or a proxy varies by the specified content encoding. Setting the cache to vary by content encoding enables ASP.NET to vary the response by the Accept-Encoding header. When a request is processed, the Accept-Encoding header is checked and the first acceptable encoding is identified and used to take one of the following actions:
If a matching encoding is also found in the HttpCachePolicy.VaryByContentEncodings list and a cached response exists, the cached response is sent.
If a matching encoding is also found in the HttpCachePolicy.VaryByContentEncodings list but a cached response does not exist, a response is generated and inserted into the cache.
If a matching encoding is not found in the HttpCachePolicy.VaryByContentEncodings list, the cache is searched for a non-encoded response, also referred to as the identity response. If the identity response is found, it is sent. Otherwise a new non-encoded response is generated and stored in the cache.
For more information about the HttpCachePolicy.VaryByContentEncodings property, see RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1, available on the tp://go.microsoft.com/fwlink/?linkid=37125. See section 14, "Header Field Definitions", for complete details.