If yo have paging, or filtering configured for your widget, they add extra URL parameters to the base URL of the page as well, for example / Each Sitefinity CMS page enters output cache using its URL as key.
This user is configured with the expected permissions required, but additional permissions may be required if your repository design deviates from the expected structure.
Leveraging output cache for your Sitefinity CMS website pages ensures your site performance and scalability.
By default, a Sitefinity CMS page has a - the one you use to access its content.
If you have a widget on the page, that displays a list of content items, each of these items has a URL, which is formed using the page base URL and the URL formatting rules for the content module.
You can define how long Sitefinity CMS should serve the old cached version of the page when it gets invalidated, as well as whether to warm-up only the page or any content details pages, served on this page a s well.
To configure the page output cache invalidation settings follow these steps: To select a warmup option that best suits your scenario you need to take two things into account - how Sitefinity CMS output cache variations work, and how your users browse your website.
Simple configure your Dispatcher Flush Agents on Publish to issue “On Trigger”.
(It is likely this has been previously configured if you are already using Publish-side flushing).
By default, when a cached version of a page is created, this version is tied to a number of dependency objects - like the content items displayed on the page, or the page template.
Editing any of the dependencies causes the cached version of the page to be invalidated.
Dispatcher Flush Rules are intended to be deployed and executed on AEM Publish, which should have On Trigger Flush Agents set up.