In XDIME 2 you control internal content caching with the meta element.
In XDIME 2 you control internal content caching with the meta element.
The default value for page caching is set in the default-scope attribute on the page-cache element in the mcs-config.xml file. The default setting is 'none'. You can override this value, or any other value that has been set as a property attribute value of 'mcs:cache-scope' on a meta tag. The 'optimistic' and 'safe' values enable caching for the page, and affect the way that MCS calculates a cache key on the content.
You can use property attribute values on the meta element to express further caching properties that may be used by services that are downstream of MCS. As with 'mcs:cache-scope', you use the mcs: namespace prefix on property attribute values.
<meta property="mcs:cache-max-age">300</meta>| Value | Description |
|---|---|
| mcs:no-cache | No caching takes place (default). If the property has one of the other possible values, caching is enabled and the cache will contain the entire content rendered for the target device. |
| mcs:cache-max-age | Value in seconds before the cache expires. Only meaningful when the cache is enabled. The mcs:max-age property is an alias for mcs:cache-max-age. |
| mcs:cache-expires | Sets an explicit expiry HTTP-date on the cache headers returned. |
| mcs:cache-auto | MCS takes into account the cache time determined by the pipeline in addition to other factors. |