With Sitefinity CMS, you can configure both client and output cache profiles on application level for pages and media libraries. You can easily create and manage global cache profiles for pages and media libraries in the Administration section of Sitefinity CMS. To do so, navigate to Administration » Settings » Global settings » Cache profiles.
NOTE: In case you need to configure cache headers, you need to do it in Sitefinity CMS Advanced settings section. For more information, see Advanced settings for cache profiles section in this article.
By setting global cache profiles on application level, you get a built-it mechanism to cache pages on the client, based on controlling the cache-control header of the page, allowing to send a standard HTTP cache-control header that instructs the client to cache the page for the configured time. You thus optimize your site's performance by reducing the number of requests on the original server by caching the page response on browser, proxy server or CDN for a specific amount of time and reused in other subsequent requests.
NOTE: You cannot delete default cache profiles.
For each cache profile, you can see the details, summarized in the following table.
Specifies the location of the cached HTTP response content. You can choose one of the following values:
Indicates the maximum size in KB to be cached. The items that exceed this limit are not cached.
NOTE: This setting only affects the cache profiles for media libraries.
We recommend that you turn off the library server caching for media libraries using the file system blob
To configure cache headers, navigate to Administration » Settings » Advanced » System » Output Cache Settings. Depending on whether you are configuring the profile for pages or media content, you have different set of built-in cache headers.
The following table describes the built-in cache headers for pages and media content.
Indicates whether the cache varies by user agent (browser) header. Applies to the Response.Cache.VaryByHeaders.UserAgent ASP.NET property.
Sets the Cache-Control: no-store HTTP header.
Sets the Cache-Control HTTP header to either the must-revalidate or the proxy-revalidate directives based on the supplied enumeration value.
Specifies whether the response should contain the vary:* header when varying by parameters.
NOTE: You can set this property either in the Advanced settings section, or when defining the cache profiles for media content in the Global settings » Cache profiles section.
To configure cache headers:
NOTE: For the media content cache header, you need to enter a value in numbers as you are setting size in KB.
You can also add a new cache header with its own logic. For more information see For developers: Add custom cache headers.
Back To Top