dispatcher cache | Community
Skip to main content
P
Punith_Shetty
Level 2
October 16, 2015
Solved

dispatcher cache

  • October 16, 2015
  • 4 replies
  • 2162 views

Hi

In dispatcher i need to clear the cache for a component which basically reads a value which will be incremented in publish Mode.But because of the caching in the dispatcher mode, old values are retreived. But the component functionality works fine in publish mode.

 

EX: Suppose a value get incremented on clicking a button, I need to display the value based on the counter.

IN Publish: Most recent update is rendered.

But in dispatcher: Old values are getting rendered because of the caching.Suppose if i append somethng like http://sample.com?1234 

then since the url is not cached,then the component displays the most recent entries.

 

 

 

So is there a way to disable the caching for ceratin pages in dispatcher mode

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 Ojjis

Well you could also do as you did in your first post. This is usually how CQ/AEM solves the problem with some includes that it don't want to be cached. Eg. in the javascript api there are methods for this where it simply adds a timestamp (as a querystring) to links that are supposed to be non-cachable. So your original solution seems like the right approach there if you don't want to configure the dispatcher.

/Johan

4 replies

Ojjis
Ojjis
Level 7
October 16, 2015

Hi punith this is absolutely possible.
In the dispatcher.any file there is a caching section where you tell the dispatcher what to cache. In the rules section you could add this:
 

/rules { /0000  { /glob "*" /type "allow" } /0001  { /glob "/path/to/noncachablefile*" /type "deny" } }

This first allows everything but later denies caching for your certtain file.

Good Luck
/Johan

Scott_Brodersen
Scott_Brodersen
Level 8
October 16, 2015

To add to what Johan said, here are some links to the docs:

scott

P
Punith_ShettyAuthor
Level 2
October 16, 2015

Thanks Johan and Scott,

But is there any way, though which the same can be achieved programatically.

 

Thanks

Ojjis
OjjisAccepted solution
Level 7
October 16, 2015

Well you could also do as you did in your first post. This is usually how CQ/AEM solves the problem with some includes that it don't want to be cached. Eg. in the javascript api there are methods for this where it simply adds a timestamp (as a querystring) to links that are supposed to be non-cachable. So your original solution seems like the right approach there if you don't want to configure the dispatcher.

/Johan

Terms & ConditionsAccessibility statement

Loading footer...