Invalidate cache with one CURL commnad | Community
Skip to main content
M
Mahesh_Vikram
Level 4
January 23, 2017
Solved

Invalidate cache with one CURL commnad

  • January 23, 2017
  • 4 replies
  • 15311 views

Hi All,

After every PROD deployment we were clearing entire cache, with the below CURL.

curl -H "CQ-Action: DELETE" -H "CQ-Handle: /" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" --noproxy .com http://<HostName>:80/dispatcher/invalidate.cache

We had a thought rather that clearing entire cache, we will invalidate it, we tried few CURL's below:-

This did not work for root portion:-

curl -H "CQ-Action: Activate" -H "CQ-Handle: /" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" --noproxy .com http://<HostName>:80/dispatcher/invalidate.cache

It worked when we have included specific site caching path as below, this will create a big script we need to modify when ever new sites gets added:-

curl -H "CQ-Action: Activate" -H "CQ-Handle: /content/<sitename>" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" --noproxy .com http://<HostName>:80/dispatcher/invalidate.cache

Is there any way we can invalidate cache with one command.

Thanks,

Viki

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

Hi,

the easiest way to invalidate the dispatcher cache would be to execute a command like this on the system where the dispatcher runs:

$ find . -name ".stat" -exec touch {} \;

This touches every stat file and marks the files as invalid.

kind regards,
Jörg

4 replies

jantzen_b
Adobe Employee
jantzen_bAdobe Employee
Adobe Employee
January 23, 2017

Hi Viki,

Are you using Akamai to host your DTM environment or are you self-hosting?

Thank you,
Jantzen

M
Mahesh_VikramAuthor
Level 4
January 24, 2017

Hi Jantzen,

We dont have Akamai, we are self hosting.

Thanks,

viki

jantzen_b
Adobe Employee
jantzen_bAdobe Employee
Adobe Employee
February 8, 2017

Hi Viki,

I spoke with a DTM engineer about this and he recommended speaking with the AEM team since this is specific to AEM. I'm going to move this thread to our AEM community. The community there is very active and you should have better luck finding an answer.

 

Regards,
Jantzen

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
February 8, 2017

Hi,

the easiest way to invalidate the dispatcher cache would be to execute a command like this on the system where the dispatcher runs:

$ find . -name ".stat" -exec touch {} \;

This touches every stat file and marks the files as invalid.

kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...