您可以尝试使用的HttpResponse。Cache属性是否会有所帮助:
Response.Cache.SetExpires(DateTime.Now.AddSeconds(60));
Response.Cache.SetCacheability(HttpCacheability.Public);
Response.Cache.SetValidUntilExpires(false);
Response.Cache.VaryByParams["Category"] = true;
if (Response.Cache.VaryByParams["Category"])
{
//…
}
或者可能会与HttpResponse.CacheControl完全封锁网页的缓存,但有利于Cache属性之上的它的被弃用:
Response.CacheControl = “No-Cache”;
或者你可以真的去坚果和手工做这一切:
Response.ClearHeaders();
Response.AppendHeader(“Cache-Control”, “no-cache”); //HTTP 1.1
Response.AppendHeader(“Cache-Control”, “private”); // HTTP 1.1
Response.AppendHeader(“Cache-Control”, “no-store”); // HTTP 1.1
Response.AppendHeader(“Cache-Control”, “must-revalidate”); // HTTP 1.1
Response.AppendHeader(“Cache-Control”, “max-stale=0″); // HTTP 1.1
Response.AppendHeader(“Cache-Control”, “post-check=0″); // HTTP 1.1
Response.AppendHeader(“Cache-Control”, “pre-check=0″); // HTTP 1.1
Response.AppendHeader(“Pragma”, “no-cache”); // HTTP 1.1
Response.AppendHeader(“Keep-Alive”, “timeout=3, max=993″); // HTTP 1.1
Response.AppendHeader(“Expires”, “Mon, 26 Jul 1997 05:00:00 GMT”); // HTTP 1.1
Reference
来源
2010-12-08 12:09:38
vic
对于一个好问题+1。好的问题+1仅仅因为糟糕的结论而击败-1。 – 2010-04-21 22:37:06
那是我的懒惰〜会再试一次 – Eatdoku 2010-04-21 23:39:57