Dispatcher caching when using Sling selectors

[AadhiraRa]

Hi Community,

I am working on an AEM as a Cloud Service project and facing an issue with Dispatcher caching. When I request pages with different Sling selectors, they are getting cached as the same response. For example, /content/my-site/page.print.html and /content/my-site/page.pdf.html both return the same cached content even though the selector is different.

How can I configure Dispatcher in AEMaaCS so that different selectors are cached separately?

Thanks for your help!

[SantoshSai]

Hi @AadhiraRa,

By default, the Dispatcher only considers the path and extension when creating a cache key, so different Sling selectors can end up being cached as the same file. To fix this, you need to update your Dispatcher configuration so that selectors are included when generating the cache entry.

In AEMaaCS you can do this by updating the dispatcher/src/conf.dispatcher.d/filters and dispatcher/src/conf.dispatcher.d/rules so that selectors are not ignored, and also making sure your cache section includes selectors in the cache file name.

For example, in the cache configuration (dispatcher/src/conf.dispatcher.d/cache/rules.any), you can add something like:

/rules {
  /0001 { /glob "*" /type "allow" }
}

And in your dispatcher.any (or farm file), make sure you have:

/ignoreUrlParams {
  /0001 { /glob "*" /type "deny" }
}

This way Dispatcher will treat /page.print.html and /page.pdf.html as different cache files instead of reusing the same one.

Reference: https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/dispatche...