The Sitefinity CMS output cache mechanism invalidates a page from cache when someone edits the page or one of the cache dependencies for that page, for example the template it’s based on or some of the content items displayed on this page. When someone request the page for the first time, Sitefinity CMS creates a cache item, and serves the page from cache for consecutive requests. This behavior helps serving pages faster and guarantees the website scalability. However, there are cases, where you might want to prevent creating a cached item of the page. For example, when a backend user is editing a page and they view it to observe the changes they’ve made, by default their request creates a cached version of the page, and this version is served to all users afterwards until the cache of the page expires. This behavior might be undesirable for two reasons:
By default, Sitefinity CMS disables output cache for logged in users in the following scenarios:
You can customize the default behavior and manually configure the default set of roles, for which output cache is disabled. To do that, follow these steps:
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important