Orchard OutputCache and OutputCache HttpModule

[orchardbot]

@jtkech created:
https://orchard.codeplex.com/workitem/21331

Following the recent discussions on OutputCache in the Committee videos, about public caching, iis kernel cache, and the potential issue with the capture stream...

So, especially if Orchard OutputCache remains not compatible with some content types (but not only), and because the HttpModule is no longer removed in web.config (I didn't notice that), my idea here is to be able, for a specific controller action, to prevent Orchard caching and use the OutputCache HttpModule in a normal way

This, not only with ignoredUrls if many different files can be served by a controller, but maybe by only testing if an [outputCache] attribute is used, even with Duration > 0 and NoStore = false. Of course, for these specific content types we will not have the same Orchard caching rules, but the ability to use e.g all the OutputCacheLocation options...

I've done some tests, with an image file (23 kb) served by a controller, to see server side caching response times. Note that here I don't talk about kernel cache because I never use "HttpCacheability.Public" in my tests, this with maxAge = 0 when testing Orchard caching, and with the "OutputCacheLocation.Server" option on an [outputCache] attribute when only testing the OutputCache HttpModule
.

No caching at all: Response time 12 ms

Orchard caching, maxAge = 0 => no proxies / client caching: Response time 6 ms

HttpModule, [OutputCache] attribute with Duration > 0, and OutputCacheLocation.Server => Cache-Control: no-cache, but caching is done on server: Response time 3 ms

Best

[orchardbot]

@jtkech commented:

Daniel answered me here
#3
his explanations and what he proposes are perfect for me
Thanks