You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
David San Filippo edited this page Sep 11, 2017
·
1 revision
Category
Notes
Module Location
Feature.Caching
Recommended
Always
Default
On
Dependencies
Features that leverage the feature cache expect this to clear the cache on Publish.
Pipelines Targeted
None
Events Targeted
Publish End, Publish End Remote
Site Settings
None
Page Settings
None
Patch Config
Feature.Cache\CacheCleaner.config
This feature ensures that all caches are properly flushed on publish. This includes not only the cache leveraged by other ASF features, like 301 Redirects and Sitemaps, but also the out of the box "Sitecore" HTML cache.
Out of the box, that cache doesn't automatically get cleared on publish, but instead requires a manual configuration for every site definition. This feature overrides the behavior automatically clearing the cache for every site in the site definition.
Note that these features are decoupled into separate event handlers and can be manually configured independently if desired, though the configuration includes targeting both event handlers for publish end and publish end remote events.
If you want to cache your own data and ensure it’s cleared on publish, you can simple use the “HttpRuntime.Cache” to manage it and this feature will clear it on publish.