Hi @krishna_chaita2,in that case, I think you will need to add some custom code and set the appropriate headers. This can be achieved with either a Filter or a Servlet. Maybe something like this:@Override public void doFilter(final ServletRequest request, final ServletResponse response, final Filter...

Hi @krishna_chaita2,in case you want to avoid customizations in /apps, you can try to upload your static HTML page in /content/dam and remove the text/html mime type from DamContentDispositionFilter. Hope this helps,Daniel  

Hi @Ravi_Joshi,check if your replication-service user has jcr:readAccessControl permissions on the root path. Good luck,Daniel

Hi @NeilKe,I haven't used Redirect Manager from ACS Commons but your logic sounds OK. In case an OSGi component has the "policy = ConfigurationPolicy.REQUIRE" parameter set, then it only gets activated when you configure it on a specific environment. Good luck,Daniel

I think you definitely need to add a piece of custom JS here. As your logic is based on user interaction, this cannot be achieved on the server. I don't see how HTL templates could help here. Good luck,Daniel

Hi @sofiyans8042875,this is for sure possible. With every CDN, including the Adobe-managed Fastly, you can redirect traffic to different origin servers. See https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-configuring-traffic#origi...

Hi @jezwn,can you share an example URL you are using to retrieve the asset from DM?Do you have Smart Imaging feature enabled?

Hello,In my project, we have been using classic Dispatcher stat level-based invalidation from the start. This worked fine until we didn't add a lot of content fragments, custom APIs, etc. Now we need custom Dispatcher flush logic to invalidate API paths or pages using queries to fetch the data from ...

I can confirm what @EstebanBustamante said. Interestingly, overlay doesn't work but you can still copy-paste stuff from /libs to /apps, delete what you don't need, and extract it with a package to your codebase. Good luck,Daniel

Hi @VivekSr1,which version of AEM are you using? In case you are on AEMaaCS there are significant differences between the local SDK and DEV. Therefore some issues can only be observed on DEV - a real Cloud instance.Did you overlay the component correctly in the /app folder? See https://experiencelea...