Hi   My application requires two SDI configurations: one for fetching dynamic content from the publisher, which is set up with a no-cache filter, and another to cache XF content for delivery from the cache.   While the first SDI is functioning as expected, the second SDI is not picking up any conten...

HI Mahedi    I have created an additional SDI (Server-Side Include) configuration for an Experience Fragment (XF) and updated all the necessary settings in the cache and filters within the Dispatcher. However, after updating the content, the Experience Fragment is not reflecting the latest changes. ...

Hi All   What are the possible reasons Akamai redirects every request to the dispatcher for secured and non-secured content, and how does the dispatcher serve that content?     Thanks KNan

Hi All  We are using Akamai CDN, and my content is served from the dispatcher cache. However, I’ve configured the headers at the dispatcher level to set Cache-Control to no-cache and no-store. How is it that the dispatcher is still serving cached content instead of Akamai?   Thanks KNan    

Thanks Mahedi ..Ill check and update .   Thanks KNan

Hi All,   I’m encountering an issue with XF publishing. Currently, when XF is published, all the reference pages clear the cache through an event handler. This is based on some older code.   I want to use SDI for XF caching, but my project already uses SDI with about some dynamic components mapped t...

Hi @Vani1012  Index Names :   An index definition can fall into one of the following categories: Out-of-the-box (OOTB) index. For instance: /oak:index/cqPageLucene-2 or /oak:index/damAssetLucene-8.   Customization of an OOTB index. These are indicated by appending -custom- followed by a numerical id...

Hi @GrishmaBa    Please try like this, <ul data-sly-list.child="${currentPage.listChildren}">  <li>${childList.first}</li></ul> The following default variables are available within the scope of the list: item: The current item in the iteration. itemList: Object holding the following properties: inde...

Hi @JakeCham  This will provide you with additional information regarding flush strategies. Deep-dive into AEM dispatcher’s cache flush strategies Thanks 

Hi @JakeCham    The /invalidate property defines the documents that are automatically invalidated when content is updated. With automatic invalidation, Dispatcher does not delete cached files after a content update, but checks their validity when they are next requested. Documents in the cache that ...