Adobe Experience Manager Sites & More

SrinivasanPa1 · 1/28/24

Hi,

When we update any content and activate aem pages from author to publish, the changes can be seen in the dispatcher url only after hard refresh of the browser cache. What settings we can check to fix this issue.

Note: AEM version is 6.5 and CDN is used in conjunction with the dispatcher.

Raja_Reddy · 1/28/24

Hi @SrinivasanPa1

Dispatcher Caching:
- Cache Headers: Make sure that the dispatcher is configured to send appropriate cache headers. These headers influence how browsers and proxies cache content. The Cache-Control and Expires headers can be set to control caching behavior.
- Dispatcher Flush Agents: AEM has replication agents called flush agents that can be configured to invalidate or flush the cache in the dispatcher when content is activated. Verify that these agents are configured correctly.
AEM Configuration:
- Dispatcher Flush: Ensure that your AEM configuration is set up to send flush messages to the dispatcher when content is activated. This is typically configured in the replication agents.
- Cache Configuration: Check your AEM instance's cache settings. Navigate to the OSGi configuration for the "Adobe Granite HTML Library Manager" (/system/console/configMgr), and adjust the client-side and server-side cache settings as needed.
- https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalid...
- https://axamit.com/blog/adobe-experience-manager/dispatcher-clear-cache
- https://docs.mktossl.com/docs/experience-cloud-kcs/kbarticles/KA-17912.html

View solution in original post

Raja_Reddy · 1/28/24

Hi @SrinivasanPa1

Dispatcher Caching:
- Cache Headers: Make sure that the dispatcher is configured to send appropriate cache headers. These headers influence how browsers and proxies cache content. The Cache-Control and Expires headers can be set to control caching behavior.
- Dispatcher Flush Agents: AEM has replication agents called flush agents that can be configured to invalidate or flush the cache in the dispatcher when content is activated. Verify that these agents are configured correctly.
AEM Configuration:
- Dispatcher Flush: Ensure that your AEM configuration is set up to send flush messages to the dispatcher when content is activated. This is typically configured in the replication agents.
- Cache Configuration: Check your AEM instance's cache settings. Navigate to the OSGi configuration for the "Adobe Granite HTML Library Manager" (/system/console/configMgr), and adjust the client-side and server-side cache settings as needed.
- https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalid...
- https://axamit.com/blog/adobe-experience-manager/dispatcher-clear-cache
- https://docs.mktossl.com/docs/experience-cloud-kcs/kbarticles/KA-17912.html

arunpatidar · 1/29/24

Hi @SrinivasanPa1
You can use etag

https://developers.cloudflare.com/cache/reference/etag-headers/

https://adobe-consulting-services.github.io/acs-aem-commons/features/etag/index.html

Arun Patidar

kautuk_sahni · 1/30/24

@SrinivasanPa1 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.