[Skip to content]

Search our Site
Easysite Resource Centre


A cache is a component that transparently stores data so that future requests for that data can be served faster. Caching may be implemented on a page by page basis.

Your options

To  add caching rules to a page go to Administration -> Content -> Pages -> Caching. The following view will be presented:

Manage page caching screenshot

1. Click Add Page:

Add caching screenshot


Click Choose to select the appropriate page


Enter an appropriate caching period for the page, for example 10 minutes.

Caching Policy

Select the appropriate option:

No Cache

This policy sets the Cache-Control to no-cache header

Without a field name, the directive applies to the entire request and a shared (proxy server) cache must force a successful revalidation with the origin Web server before satisfying the request. With a field name, the directive applies only to the named field;the rest of the response may be supplied from a shared cache.

For more information, refer to RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1, available on the World Wide Web Consortium's site at http://www.w3c.org. See section 14.9 "Cache-Control" and section 13, "Caching in HTTP" for complete details.

Note: that the NoCache policy does not send the common HTTP 1.0 request directive Pragma: no-cache.


This policy will cache the page for users on an internal network and sets the Cache-Control to private to specify that the response is cacheable only on the client and not by shared (proxy server) caches. This is the Default value of the Caching Policy.


This policy will cache the page for users browsing from the server results in the client receiving a Cache-Control: no-cache directive but the document is cached on the origin server. This policy specifies that the response is cached only at the origin server, similar to the NoCache option. 


This policy will cache the page for users on a public network and sets the Cache-Control to public to specify that the response is cacheable by clients and shared (proxy) caches. 

Server And Private 

This policy indicates that the response is cached at the server and at the client but nowhere else. Proxy servers are not allowed to cache the response.

2. Click Confirm.