XF caching issue

[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 to it, all of which are set to "no cache."

From what I understand, in order to use SDI with XF, the filter setting should not be "no cache." Adjusting this setting affects the functionality of the other components.

How can we handle this situation? Specifically, how can we integrate XF into the existing SDI setup without disrupting the components that currently use the "no cache" filter?

Thanks

[Mahedi_Sabuj]

Hi @KNan, You can use two separate SDI OSGi configurations with different selectors. Ensure that caching is not disabled for the XF-based SDI configuration selectors.

https://ms-29.com/aem/dispatcher/cache-aem-pages-with-dynamic-content

https://ms-29.com/aem/experience-fragment/caching-experience-fragments

[KNan]

Thanks Mahedi ..Ill check and update .

Thanks
KNan

[KNan]

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.

Interestingly, if a page (containing the Experience Fragment) is activated, the page shows the updated XF content, which is expected behavior.

The issue seems to be that the SDI configuration for the XF is not functioning as intended. Could you please provide your insights or suggestions on why this might be happening?

Thanks

KNan

[Mahedi_Sabuj]

Hi @KNan, Can you share OSGi configs and dispatcher filter rules?