Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

How to flush dispatcher catch with custom parameter passed in page URL (AACS)

Avatar

Level 9

Hello,

 

What is the best way to flush on demand dispatcher cache for certain pages in site using a URL query parameter (AEM as a cloud service). Please share some config. We used IgnoreURLParams but did not work correctly.

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/conten...

 

from above url we understood that there is only two ways to do it Sling Content Distribution or Replication. we want to avoid custom development using option Sling Content Distribution and looking some suggestions here.

 

Thanks,

Pawan

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

ignoreUrlParams has nothing to do with dispatcher cache flushing. It's a way to achieve a higher cache hit ratio on the dispatcher by ignoring certain query parameters.


To your question: Why do you want to invalidate the dispatcher cache, outside of regular activations/deactivations? That should not be necessary.

View solution in original post

2 Replies

Avatar

Community Advisor

Hi @Pawan-Gupta , you may try to republish the set of pages for cache invalidation - this can be a tree activation as well, Publishing will help with dispatcher cache invalidation if you want to avoid custom development. Flush gets auto-triggered on publish/unpublish action.

For IgnoreURLParams, kindly check if the corresponding section is uncommented in dispatcher config.
Reference: Configuring Dispatcher | Adobe Experience Manager

Avatar

Correct answer by
Employee Advisor

ignoreUrlParams has nothing to do with dispatcher cache flushing. It's a way to achieve a higher cache hit ratio on the dispatcher by ignoring certain query parameters.


To your question: Why do you want to invalidate the dispatcher cache, outside of regular activations/deactivations? That should not be necessary.