根据各种文章(例如
here和
here),可以缓存ASP.NET MVC操作的属性结果,并且在调用控制器操作时不再执行.

在我的情况下,这种行为是不可取的(例如,我有一个基于我自己的属性和IP的授权系统,每次都需要执行的角色检查,以及其他事情).

如何阻止ASP.NET MVC缓存我的属性/属性执行结果并保证每次都执行它们？

解决方法

查看AuthorizeAttribute的源代码(在Codeplex上或通过Reflector),了解如何关闭授权页面的缓存.我将它重构为我的自定义授权属性的单独方法,该属性派生自AuthorizeAttribute.

protected void CacheValidateHandler( HttpContext context,object data,ref HttpValidationStatus validationStatus )
{
    validationStatus = OnCacheAuthorization( new HttpContextWrapper( context ) );
}

protected void SetCachePolicy( AuthorizationContext filterContext )
{
    // ** IMPORTANT **
    // Since we're performing authorization at the action level,the authorization code runs
    // after the output caching module. In the worst case this could allow an authorized user
    // to cause the page to be cached,then an unauthorized user would later be served the
    // cached page. We work around this by telling proxies not to cache the sensitive page,// then we hook our custom authorization code into the caching mechanism so that we have
    // the final say on whether a page should be served from the cache.
    HttpCachePolicyBase cachePolicy = filterContext.HttpContext.Response.Cache;
    cachePolicy.SetProxyMaxAge( new TimeSpan( 0 ) );
    cachePolicy.AddValidationCallback( CacheValidateHandler,null /* data */);
}