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

Akamai response validate steps

Avatar

Level 3

Hi Team,

I have created akamai API call to invalidate the URI in my project. iam able to get the response but after getting response where i need to check what are files are cached .can anyone please suggest where i need to check for know the files cached during akami api invoke with success code.

 

Please find my response status below.

 

akamai response body : {"httpStatus":201,"detail":"Request accepted","supportId":"eiup-P2pqZYW3v8Ujddwy7PhTo6","purgeId":"eiup-P2pqZYW3v8Ujddwy7PhTo6","estimatedSeconds":5}

akamai response statusLine : HTTP/1.1 201 Created

akamai response statusLine.getStatusCode : 201

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hey @mohanasundaramp if you're getting this response from Akamai then that means your URI cache has been purged. You must be sending an INVALIDATE/DELETE request to Akamai using their Fast Purge V3 API.

 

Coming to validating whether cache for those path(s) was cleared, you can turn off the cache purge agent(or whatever way you are sending the request to Akamai, may be while externalizing the URIs, you can mess with the externalizer.PPUBLISH confiuration or just mess temporarily with your API tokens) and then publish the content.

 

You must be shown cached content from Akamai, then you enable/correct the configuration and publish the content and refresh the page : this time you should be able to get the refreshed content.

In order to check what files(based on extension) are being cached, you need to login to Akamai and go to your respective property and take a look:

bilala23933647_0-1618213260777.png

 

There will be other properties to look at as well!

Hope that helps,

Bilal.



View solution in original post

2 Replies

Avatar

Community Advisor

Hi @mohanasundaramp 

If I understand your question correctly, Akamai Invalidate/Purge will invalidate the cache. It will not create the cache file.

So if you have the already made the rquest you know based on which parameter the request has been made and it;s accepted which is why it returned 201 status code.

Requests can be made using the following approaches:

  1. urlrequest
  2. urlrequestwithhostname
  3. cpcoderequest
  4. tagrequest

https://developer.akamai.com/api/core_features/fast_purge/v3.html#data

 

Thanks!

 

Avatar

Correct answer by
Community Advisor

Hey @mohanasundaramp if you're getting this response from Akamai then that means your URI cache has been purged. You must be sending an INVALIDATE/DELETE request to Akamai using their Fast Purge V3 API.

 

Coming to validating whether cache for those path(s) was cleared, you can turn off the cache purge agent(or whatever way you are sending the request to Akamai, may be while externalizing the URIs, you can mess with the externalizer.PPUBLISH confiuration or just mess temporarily with your API tokens) and then publish the content.

 

You must be shown cached content from Akamai, then you enable/correct the configuration and publish the content and refresh the page : this time you should be able to get the refreshed content.

In order to check what files(based on extension) are being cached, you need to login to Akamai and go to your respective property and take a look:

bilala23933647_0-1618213260777.png

 

There will be other properties to look at as well!

Hope that helps,

Bilal.