Caching When Authentication is Used
The /allowAuthorized property controls whether requests that contain any of the following authentication information are cached:
- The authorization header.
- A cookie named authorization.
- A cookie named login-token.
By default, requests that include this authentication information are not cached because authentication is not performed when a cached document is returned to the client. This configuration prevents Dispatcher from serving cached documents to users who do not have the necessary rights.
However, if your requirements permit the caching of authenticated documents, set /allowAuthorized to one: /allowAuthorized "1"
Source:- Configuring Dispatcher
For Permission-sensitive caching :- Caching Secured Content
// Permission-sensitive caching enables you to cache secured pages. Dispatcher checks users' access permissions for a page before delivering the cached page.
Reference :- Permission Sensitive Caching Delivery
Must read:-Re: How to achieve gated content
Kautuk Sahni