How to flush dispatcher catch with custom parameter passed in page URL (AACS) | Community
Skip to main content
Pawan-Gupta
Level 8
June 6, 2023
Solved

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

  • June 6, 2023
  • 2 replies
  • 823 views

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/content-delivery/caching.html

 

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

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.

2 replies

Community Advisor
June 6, 2023

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

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
June 8, 2023

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.