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 toke...
Hi, Not sure if that is achievable since we would want the Akamai to
communicate to dispatcher to get desired cache detail. It is probably
better to clear dispatcher cache for all dispatchers (for the content in
question) first and then the akamai cache. What is the idea behind
knowing which dispatcher had a cache cleared?
Hello,Here is the list of ACL's required to perform different operations
on the reports:add jcr:read, rep:write acl for the group on the path
/var/dam/reports (need to save/delete the report to/from the location)
add jcr:read acl for the group on the path /libs/dam/content/reports &
/libs/dam/gui/content/nav/tools/assets/assetreports (UI access to the
reports feature)add jcr:read acl for the group on the path
/var/dam/share (access the link shares by various users)Can you check if
there are any ...