Dispatcher Clear cache cURL no longer works.

Mayukh007

14-10-2020

Hi, We use Curl to clear dispatcher cache. We issue command to ELB and ELB does the rest.

 

curl -H "CQ-Action: Delete" -H "CQ-Handle: /content/" -H "CQ-Path: /content/" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" -H "Host:www-aem-dev.manulife.ca" http://manulife-dev65-2019april28-545949682.ca-central-1.elb.amazonaws.com/dispatcher/invalidate.cac...

 

I can run it even from my local Terminal as this doe snot need any authentication. Now we are moving to Cloud Manager and suddenly the same command no longer works and I get 403

 

- Forbidden with error: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /dispatcher/invalidate.cache on this server.</p> </body></html>

 

I have not done any change in any of the allowedclient or invalidate parameters/files, it is literally same dispatcher code I am using.

Any pointer on how to fix this..?

Answers (1)

Answers (1)

Jörg_Hoh

Employee

14-10-2020

In the dispatcher configuration the cache invalidation is typically constraint to a certain network / IP range. And that's probably configured differently now than it was before. Check the dispatcher configuration for the parameter "allowedClients" (see also the documentation at https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-co...).

When you migrate to AMS, your CSE will not allow you make this functionality available to everyone (when you issue these commands via the ELB, basically everyone can execute it, not only you).

 

HTH,

Jörg