Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Dispatcher Clear cache cURL no longer works.

Avatar

Avatar
Contributor
Level 3
Mayukh007
Level 3

Likes

15 likes

Total Posts

88 posts

Correct Reply

2 solutions
Top badges earned
Contributor
Validate 1
Shape 1
Ignite 1
Give Back 5
View profile

Avatar
Contributor
Level 3
Mayukh007
Level 3

Likes

15 likes

Total Posts

88 posts

Correct Reply

2 solutions
Top badges earned
Contributor
Validate 1
Shape 1
Ignite 1
Give Back 5
View profile
Mayukh007
Level 3

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..?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Contributor
Level 3
Mayukh007
Level 3

Likes

15 likes

Total Posts

88 posts

Correct Reply

2 solutions
Top badges earned
Contributor
Validate 1
Shape 1
Ignite 1
Give Back 5
View profile

Avatar
Contributor
Level 3
Mayukh007
Level 3

Likes

15 likes

Total Posts

88 posts

Correct Reply

2 solutions
Top badges earned
Contributor
Validate 1
Shape 1
Ignite 1
Give Back 5
View profile
Mayukh007
Level 3

14-10-2020

Added this in publish and author invalidate any file

 

 

/1
{
/glob "*.*"
/type "allow"
}

Answers (1)

Answers (1)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
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