SSI mechanism, can it be extended?

[#1]

Hi AEM experts,

Need urgent help. I have a scenario.

On modification: When I make changes to my experience fragment(which renders my header), the changes are reflected in header for all the pages in author environment.

On replication: When I replicate the experience fragment, the changes are reflected to Publisher. But it does not reflect in dispatcher, all the pages reflect old header until I go and delete whole cache folder in my dispatcher. I believe cache invalidation request is not associated with experience fragment unlike content fragment.

I have implemented SDI/SSI in AEM 6.3 sites for my header component. Which resolves this issue but then I am concern about the performance of the site.

Because I believe for every page request dispatcher will render whole page from cache but it will by-pass the header component request(As it is SSI) & header will be rendered from Publisher.(Is this understanding right)

So every time my publisher will be engaged for only header component.

[#2 · Accepted solution]

The request may not go to publish server each time, you could configure it with TTL and cache for a very specific time duration on apache. You could use SDI/SSI for various use cases.

Refer to a working example in the video -

Adobe Experience Manager Help | Set up Sling Dynamic Include in AEM

Apache Sling :: Apache Sling Dynamic Include

[#3]

Dear Monendra,

I am not sure of intermediate cache you are talking about.

My understanding is that it will be requested from Publisher every single time.

Please do setup your local Apache with SSI and Publisher and try your scenario.

Regards,

Peter

[#4]

Hi Peter,

Thanks for replying.

I have one question, if we inject a component via SSI, does it mean that it will be requested from publisher everytime or does it create a intermediate cache somewhere in Apache server to render the component?

I have followed many blogs but nowhere I can get clear answer to this question of mine.

Thanks,

Monendra

[#5]

Dear Monedo,

You are absolutely, correct, it's not the best practice to serve content that can be cached from the Publisher.

Would it be possible for you to let us know what invalidation rules you have for that specific website?

Do your invalidation rules allow invalidation of experience fragments?

Would you be able to turn DEBUG level on one of your Dispatcher's in lower enviroment to see whether there is any issue during invalidation request processing?

Regards,

Peter