Custom caching

You can overrule the default caching parameters of a site by using "cache" and "expire" parameters in URLs and HCL Web Content Manager tags.

Note: Custom caching can be used only when a server's default web content cache is set to none or advanced caching. If basic caching is used as your default web Content cache, Custom caching cannot be used.
There are two basic methods in which custom caching can be used with your default server caching settings:
Default Server Caching Enabled
In this scenario, some form of default server caching is enabled. Caching parameters within connect tags and URLs can be used to either:
  • Disable caching for the data that is being requested.
  • Apply different caching parameters to the data that is being requested.

This method is used with sites that are mostly static, but that contain a few dynamic elements that require a different caching strategy from the server's default caching strategy.

Default Server Caching Disabled
In this scenario, default server caching is disabled. Caching parameters within connect tags and URLs can be used to enable caching for the data that is being requested.

This scenario is used with sites that contain many elements that require different caching strategies.