AEM Dispatcher Invalidation CQ-Action Query

[Rampai94]

Hi All,

What is the difference between "CQ-Action: Activate", "CQ-Action: Deactivate", "CQ-Action: Delete" while sending a Curl request to dispatcher to invalidate the cache?

Is there any API that lists down these methods?

Which action should be used if I simply want to touch the statsfile for the payload?

This documentation is a bit confusing as it states that the dispatcher deletes files on "CQ-Action: Activate". And the Curl Commands documentation states that "CQ-Action: Activate" is used to invalidate the cache. For evicting cache, "CQ-Action: Deactivate" is used.

Thanks,

Ram

[ChitraMadan · Accepted solution]

Hi @Rampai94 ,

This documentation has really good explanation:

https://helpx.adobe.com/uk/experience-manager/kb/ams-dispatcher-manual/disp-flushing.html

If this doesn't help, Can you please explain your scenario in a bit more detail please.

[Rampai94]

Thanks! This helped. One more query I have is how to handle the Host Header while setting up the dispatcher flush agent in case of multiple sites hosted on AEM? The example provided handles one particular site but how to ensure that the flush request goes to the correct vhost in case of like 100+ sites?

[ChitraMadan]

Hi @Rampai94 , Please refer to this article https://www.netcentric.biz/insights/2017/01/aem-dispatcher-cache-invalidation-for-multiple-cache-far...

[berliant]

Content paths can either be invalidated or flushed from the AEM Dispatcher cache.

AEM Dispatcher behavior - invalidate performs a cache invalidation, similar to when content is activated from author to publish (CQ-Action: Activate, CQ-Action: Deactivate) flush performs a cache deletion (CQ-Action: Delete).

In general, the use of the invalidate action is preferable but there may be cases where flushing is required, especially when using AEM HTML Client Libraries.

[vanegi]

These actions define the ReplicationActionType :

• ACTIVATE: Invalidates the cached files opposed to deleting
• DELETE: Deletes the cached files opposed to invalidating

And used for Dispatcher Flush agents and specify elements that must be flushed.

For a Dispatcher Flush agent the three standard entries should not need changing:

• CQ-Action:{action}
• CQ-Handle:{path}
• CQ-Path:{path}

These are used, as appropriate, to indicate the action to be used when flushing the handle or path. The sub-parameters are dynamic:

• {action} indicates a replication action
• {path} indicates a path

They are substituted by the path/action relevant to the request and therefore do not need to be “hardcoded”:

Note:

If you have installed AEM in a context other than the recommended default context, then you will need to register the context in the HTTP Headers. For example:
CQ-Handle:/<yourContext>{path}