CacheControl in ASP.NET [转]

简介:

CacheControl

The CacheControl property allows you to set the HTTP/1.1 Cache-Control header in a response.Syntax
 
Response.CacheControl [ =  Cache Control Header ]

Parameters

Cache Control Header
The following is a partial list of values supported by the HTTP/1.1 Protocol. Please see the  Hypertext Transfer Protocol -- HTTP/1.1 specification at the  World Wide Web Consortium Web site, section 14.9, for more complete descriptions.
 
Value Description
Private
A cache mechanism may cache this page in a Private cache and resend it only to a single client. This is the default value. Most proxy servers will not cache pages with this setting.
Public
Shared caches, such as proxy servers, will cache pages with this setting. The cached page can be sent to any user.
No-cache
Do not cache this page at all, even if for use by the same client.
No-store
The response and the request that created it must not be stored on any cache, whether shared or private. The storage inferred here is non-volatile storage, such as tape backups. This is not an infallible security measure.

Note

Between your Web server and a user requesting your page, there may be proxy servers configured to cache Web pages for faster response times. Usually ASP pages are developed to be unique for each user, or may contain secure information. 
 
For this reason, IIS sets this property to "Private" so that proxy servers or other cache mechanisms will not cache pages.  You can override this default value, setting it to any value supported by the HTTP/1.1 protocol, documented in the  Hypertext Transfer Protocol -- HTTP/1.1 specification at the  World Wide Web Consortium Web site.
 
If there is no cache mechanism between your Web server and a client computer, or if a proxy server is running HTTP/1.0, CacheControl will be ignored.
 
Setting CacheControl to "public" may seem to improve the performance of your .asp files, but it is discouraged if you generate custom HTML for every request, and a proxy server might interfere with the response.
 
The values for CacheControl are strings, and must be enclosed in quotation marks (" "). You must set CacheControl before any response is sent to the client unless response buffering is enabled.

Example

CacheControl comes before the <HTML> tag to ensure that it is set before content is sent to the client.
--- CacheControl_NoBuffer.asp ---
 
 
 
 
<% Response.Buffer = False Response.CacheControl = "private"%>
 
 
<HTML>
 
 
<HEAD>
 
 
<TITLE>Response.CacheControl Example</TITLE>
 
 
</HEAD>
 
 
<BODY> Output from this page is sent to the client as it is being processed.<BR>
 
 
It will not be cached.<BR> Today is <%= Date %>, <%= Time %><BR>
 
 
<H3>Please enter your credit card number:</H3>
 
 
<FORM NAME="Order" METHOD="POST" ACTION="order.asp ">
 
 
<INPUT TYPE="TEXT" NAME="CreditCard">
 
 
<INPUT TYPE="SUBMIT" VALUE="Submit" NAME="Submit">
 
 
</FORM>
 
 
</BODY>
 
 
</HTML>
--- CacheControl_Buffer.asp ---
 
 
 
 
 
 
<% Response.Buffer = True %>
 
 
<HTML><HEAD><TITLE>Response.CacheControl Example</TITLE></HEAD>
 
 
<BODY> Output from this page is sent to the client once it is completely processed by
 
 
the server, so we can set CacheControl anytime.<BR>
 
 
<% Response.CacheControl = "private" %>It will not be cached.<BR>
 
 
Today is <%= Date %>, <%= Time %><BR>
 
 
<H3>Please enter your credit card number:</H3>
 
 
<FORM NAME="Order" METHOD="POST" ACTION="order.asp ">
 
 
<INPUT TYPE="TEXT" NAME="CreditCard">
 
 
<INPUT TYPE="SUBMIT" VALUE="Submit" NAME="Submit">
 
 
</FORM>
 
 
</BODY>
</HTML>
 
from:http://www.asp-dev.com/main.asp?page=94
欢迎加群互相学习,共同进步。QQ群:iOS: 58099570 | Android: 572064792 | Nodejs:329118122 做人要厚道,转载请注明出处!



















本文转自张昺华-sky博客园博客,原文链接:http://www.cnblogs.com/sunshine-anycall/archive/2010/01/13/1646250.html ,如需转载请自行联系原作者

相关文章
|
.NET 开发框架 传感器
|
.NET 开发框架 前端开发
|
.NET 开发框架 前端开发
|
Web App开发 .NET 数据安全/隐私保护
|
Web App开发 .NET 关系型数据库