Show Menu


Traffic passes through the CDN to an apache web server layer, which supports modules including the dispatcher. In order to increase performance, the dispatcher is used primarily as a cache to limit processing on the publish nodes. Rules can be applied to the dispatcher configuration to modify any default cache expiration settings, resulting in caching at the CDN. Note that dispatcher also respects the resulting cache expiration headers if enableTTL is enabled in the dispatcher configuration, implying that it will refresh specific content even outside of content being republished.
This page also describes how dispatcher cache is invalidated, as well as how caching works at the browser level with regards to client-side libraries.



  • by default, cached by the browser for five minutes, based on the cache-control header emitted by the apache layer. The CDN also respects this value.
  • can be overridden for all HTML/Text content by defining the EXPIRATION_TIME variable in global.vars using the AEM as a Cloud Service SDK Dispatcher tools.
  • can be overridden on a finer grained level by the following apache mod_headers directives:
<LocationMatch "\.(html)$">
        Header set Cache-Control "max-age=200"

You must ensure that a file under src/conf.dispatcher.d/cache has the following rule (which is in the default configuration):
{ /glob "*" /type "allow" }

  • To prevent specific content from being cached, set the Cache-Control header to "private". For example, the following would prevent html content under a directory named "myfolder" from being cached:
<LocationMatch "\/myfolder\/.*\.(html)$">.  // replace with the right regex
    Header set Cache-Control “private”

Client-Side libraries (js,css)

  • by using AEM's Client-Side library framework, JavaScript and CSS code is generated in such a way that browsers can cache it indefinitely, since any changes manifest as new files with a unique path. In other words, HTML that references the client libraries will be produced as needed so customers can experience new content as it is published. The cache-control is set to "immutable" or 30 days for older browsers who don't respect the "immutable" value.
  • see the section Client-side libraries and version consistency for additional details.

Images and any content large enough stored in blob storage

  • by default, not cached
  • can be set on a finer grained level by the following apache mod_headers directives:
<LocationMatch "^.*.jpeg$">
    Header set Cache-Control "max-age=222"

It is necessary to ensure that a file under src/conf.dispatcher.d/cache has the following rule (which is in the default configuration):
{ /glob "*" /type "allow" }

Make sure that assets meant to be kept private rather than cached are not part of the LocationMatch directive filters.

Other content file types in node store

  • no default caching
  • default cannot be set with the EXPIRATION_TIME variable used for html/text file types
  • cache expiration can be set with the same LocationMatch strategy described in the html/text section by specifying the appropriate regex

Dispatcher Cache Invalidation

In general, it will not be necessary to invalidate the dispatcher cache. Instead you should rely on the dispatcher refreshing its cache when content is being republished and the CDN respecting cache expiration headers.

Dispatcher Cache Invalidation during Activation/Deactivation

Like previous versions of AEM, publishing or unpublishing pages will clear the content from the dispatcher cache. If a caching issue is suspected, customers should republish the pages in question.
When the publish instance receives a new version of a page or asset from the author, it uses the flush agent to invalidate appropriate paths on its dispatcher. The updated path is removed from the dispatcher cache, together with its parents, up to a level (you can configure this with the statfileslevel .

Explicit dispatcher cache invalidation

In general, it won't be necessary to manually invalidate content in the dispatcher, but it is possible if needed, as described below.
Prior to AEM as a Cloud Service, there were two ways of invalidating the dispatcher cache.
  1. Invoke the replication agent, specifying the publish dispatcher flush agent
  2. Directly calling the invalidate.cache API (for example, POST /dispatcher/invalidate.cache )
The dispatcher's invalidate.cache API approach will no longer be supported since it addresses only a specific dispatcher node. AEM as a Cloud Service operates at the service level, not the individual node level and so the invalidation instructions in the Invalidating Cached Pages From AEM page are not longer valid for AEM as a Cloud Service . Instead, the replication flush agent should be used. This can be done using the Replication API. The Replication API documentation is available here and for an example of flushing the cache, see the API example page specifically the CustomStep example issuing a replication action of type ACTIVATE to all available agents. The flush agent endpoint is not configurable but pre-configured to point to the dispatcher, matched with the publish service running the flush agent. The flush agent can typically be triggered by OSGi events or workflows.
The diagram presented below illustrates this.


If there is a concern that the dispatcher cache isn't clearing, contact customer support who can flush the dispatcher cache if necessary.
The Adobe-managed CDN respects TTLs and thus there is no need fo it to be flushed. If an issue is suspected, contact customer support support who can flush an Adobe-managed CDN cache as necessary.

Client-Side libraries and Version Consistency

Pages are composed of of HTML, Javascript, CSS, and images. Customers are encouraged to leverage the Client-Side Libraries (clientlibs) framework to import Javascript and CSS resources into HTML pages, taking into account dependencies between JS libraries.
The clientlibs framework provides automatic version management, meaning that developers can check in changes to JS libraries in source control and the latest version will be made available when a customer pushes their release. Without this, developers would need to manually change HTML with references to the new version of the library, which is especially onerous if many HTML templates share the same library.
When the new versions of libraries are released to production, the referencing HTML pages are updated with new links to those updated library versions. Once the browser cache has expired for a given HTML page, there is no concern that the old libraries will be loaded from the browser cache since the refreshed page (from AEM) now is guaranteed to reference the new versions of the libraries. In other words, a refreshed HTML page will include all the latest library versions.
The mechanism for this is a serialized hash, which is appended to the client library link, ensuring a unique, versioned url for the browser to cache the CSS/JS. The serialized hash is only updated when the contents of the client library changes. This means that if unrelated updates occur (i.e no changes to the underlying css/js of the client library) even with a new deployment, the reference remains the same, ensuring less disruption to the browser cache.

Enabling Longcache versions of Client Side Libraries - AEM as a Cloud Service SDK Quickstart

Default clientlib includes on an HTML page look like the following example:
<link rel="stylesheet" href="/etc.clientlibs/wkndapp/clientlibs/clientlib-base.css" type="text/css">

When strict clientlib versioning is enabled, a long term hash key is added as a selector to the client library. As a result, the clientlib reference look like this:
<link rel="stylesheet" href="/etc.clientlibs/wkndapp/clientlibs/" type="text/css">

Strict clientlib versioning is enabled by default in all AEM as a Cloud Service environments.
To enable strict clientlib versioning in the local SDK Quickstart perform the following actions:
  1. Navigate to the OSGi Configuration manager <host>/system/console/configMgr
  2. Find the OSGi Config for Adobe Granite HTML Library Manager:
    • Check the checkbox to enable Strict Versioning
    • In the field labeled Long term client side cache key, enter the value of /.*;hash
  3. Save the changes. Note that it is not necessary to save this configuration in source control since AEM as a Cloud Service will automatically enable this configuration in dev, stage and production environments.
  4. Any time the contents of the client library are changed, a new hash key is generated and the HTML reference will be updated.