# client libraries are now versioned so new ones can be cached for a long time<Location ~ "(\.min)?\.[a-f0-9]+\.(js|css)$"> # Important - Cache control is set to immutable by AEM Header unset Cache-Control Header always set Cache-Control: max-age=2592000</Location>hi Daniel,I put this in each ...

Thanks Daniel,The documentation says to add this, I assume to the IfModule mod_headers.c part of the vhost files.SetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.js" long_expires=trueSetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.css" long_expires=trueHeader set Cache-Control max-age=2592000 env=long_expiresI...

Thanks Esteban,That is interesting too.It looks like  I have a choice between (i) changing the clientlib names to ones with hashes in themas explained above, and setting max-age to 0.or (ii) do what you suggest above. Use ACS commons to put cache-control headers on requests by creating a OSGi config...

Thanks Prathyusha,I can't find that text in our codebase .But I can ask our Adobe Customer support guy if that .htaccess file with that configuration is on our production dispatchers.

Thanks, no, I have nothing like that. The cache-control must be coming from somewhere else.I see I do have a configuration for com.adobe.granite.ui.clientlibs.impl.HTMLLibraryManagerImpl.xml where the htmllibmanager.maxage is set to -1.I don't know if that configuration gives or takes away Headers

Thanks Mukesh,There is currently no configuration for CACHE-CONTROL in any of our dispatcher vhosts file.So I am wondering where this header comes from (for some, not all of the sites.) We have managed AWS, not cloud and not with a CDN. Is it coming from some default in AEM ? Or from upstream somewh...

Also, we don't have a CDN

Thanks everyone for replying. I am puzzled that I am getting the CACHE-CONTROL header for some of my sites, but my main site has no CACHE-CONTROL parameter.  (SO I don't have the delay in deploying new code problem there.)  There is no difference in the vhosts files for any of the sites. Has anyone ...

hi folks,Recently we noticed that one of our sites wasn't showing code updates we made via Cloud Manager.We found that there was a CACHE-CONTROL header with max-age of an hour. Sure enough, after the hour, the code updated. I cannot find this parameter configured in our AMS AEM 6.5.20 installation. ...

Thanks! It is building now!