Closed gareththackeray closed 2 years ago
I fixed my first commit with a forced push and have now added a second that makes a second check for SkipByCustom before actually caching the response. This means that you can have an action that (say) sets something into HttpContext.Items to indicate that this particular response should not be cached.
I'll have a look very soon, I'm quite busy atm with other projects.
Kind regards.
Sometimes you want to allow the cache to be bypassed entirely. For example if you are in draft mode and you want to preview your changes with a query string parameter or something.
So I've written a SkipByCustom feature that works analogously to VaryByCustom but the delegate returns a bool which then ordains whether the thing should bypass the cache.
Not sure if you'll want to go for this or not. If you do then I can add a little documentation.
Thanks for writing the library in the first place!