Avoid clientside cache of JS and CSS in AEM

[akhilraj]

Hi,

We have implemented SAML configuration in AEM and post that Dispatcher is not creating any cache.

But we observed that, browser is creating cache for JS and CSS and if any change happening for JS/CSS will not reflect properly until user clear browser cache.

How we can avoid caching of clientlibs in AEM ?

Updating Media

[Ritesh_Mittal · Accepted solution]

Hi @akhilraj ,

Clientlib versioning will resolve this issue. I am assuming you are using AEM on premise since AEM as cloud comes with OOTB Strict clientlib versioning.

On premise -

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

Cloud -

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/conten...

Thanks,

Ritesh Mittal

[akhilraj]

Hi @Ritesh_Mittal ,

I tried the steps to make it work.

But initial step of copying itself is providing below error.

Anything else we have to do for this?

[Ritesh_Mittal]

Have you tried restarting your AEM instance?

[akhilraj]

Hi @Ritesh_Mittal ,

Have done the changes and now it is working.

If we do some js changes and replicate, the number is changing and changes are reflecting properly.

But after how much time, again same file will load from cache ? Now I can see updated file is always loading from server after versioning.

But it should load from cache if there is no change, right ?

[EstebanBustamante]

This is a hot topic, and there are several techniques used, but specifically for clientlibs, I would recommend if you are on Premise to use the Versioning Clientlibs from ACS Commons and if you are on Cloud, you can take advantage of versioning client library URLs.