OutputCache Bug with VaryByParam=“None” with MVC RC refresh?
VaryByParam="*" will create a new cache for every different parameter passed VaryByParam="None" will create one and only one cache, regardless of parameters.
VaryByParam="*" will create a new cache for every different parameter passed. VaryByParam="None" will create one and only one cache, regardless of parameters.
I meant VaryByParam="" not VaryByParam="" cause the bug still exists with VaryByParam="" – Celik Mar 3 '09 at 16:02.
Route elements are not considered parameters for OutputCache. What is VaryByParam in asp. Net?
Came across to this defect with ASP.NET RC refresh while using VaryByParam="" instead of VaryByParam="None". Caching WORKS, but page http://www.yoursite.com and http://www.yoursite.com/home/index will be cached separately it seems. What is the difference between VaryByParam="" and VaryByParam="None"?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
ASP.Net MVC Output Caching: The directive or the configuration settings profile must specify the 'varyByParam' attribute?
Partial Page Caching and VaryByParam in ASP.NET MVC 3?
OutputCache behavior in ASP.NET MVC 3?
Outputcache override with query string showing non cache version in asp.net mvc?
ASP.NET MVC hits outputcache for every action?
How can I remove the cache of a page (cached with VaryByParam) for certain request params in code?