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

Invalidate cache with one CURL commnad

Avatar

Level 5

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

4 Replies

Avatar

Level 10

Hi Viki,

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

Thank you,
Jantzen

Avatar

Level 5

Hi Jantzen,

We dont have Akamai, we are self hosting.

Thanks,

viki

Avatar

Level 10

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

Avatar

Correct answer by
Employee Advisor

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