Provides enumerated values that are used to set the Cache-Control HTTP header.
Assembly: System.Web (in System.Web.dll)
|Sets the Cache-Control: no-cache header. Without a field name, the directive applies to the entire request and a shared (proxy server) cache must force a successful revalidation with the origin Web server before satisfying the request. With a field name, the directive applies only to the named field; the rest of the response may be supplied from a shared cache.|
|Default value. Sets Cache-Control: private to specify that the response is cacheable only on the client and not by shared (proxy server) caches.|
|Sets Cache-Control: public to specify that the response is cacheable by clients and shared (proxy) caches.|
|Specifies that the response is cached only at the origin server. Similar to the option. Clients receive a Cache-Control: no-cache directive but the document is cached on the origin server. Equivalent to .|
|Applies the settings of both and to indicate that the content is cached at the server but all others are explicitly denied the ability to cache the response.|
|Indicates that the response is cached at the server and at the client but nowhere else. Proxy servers are not allowed to cache the response.|
For more information, go to RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1, on the World Wide Web Consortium (W3C) Web site. In particular, for complete details, see Section 14.9 "Cache-Control" and Section 13, "Caching in HTTP."
NoCache does not send the common HTTP 1.0 request directive Pragma: no-cache.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.