@Shashi_Mulugu , The image is being rendered from the srcset rather than the src. When I hover over the img tag, it usually shows the rendered size and the aspect ratio of the image matches the Tablet mode rather than the Mobile mode as per our image profiles.

Hi, I used the same approach as described in the link below to implement. For me, it works. https://www.youtube.com/watch?v=R9b38PXjBzQ&ab_channel=TechTalkwithRitesh.

Hi @arunpatidar,   Thank you for sharing your thoughts, I have went to the above reference link. It was hugely helpful. How can we cache the response in the /var/yourproj/feature/cache folder? If you could please provide a link, that would be greatly appreciated.

Thanks, Based on the requirements, we are experimenting with different TTL and when to clear the cache.

@SantoshSai sorry for the delay. Thank you for providing the code. We are calling third-party services via Models and Servlets, as well as AEM rendering.To cache the Model's and Servlet's third-party responses, we are using the Ehcache technique. 

@SantoshSai , @RajaShankar  For all C2 components on the page, I'm getting the same value. @RajaShankar I believe you are correct, however @SantoshSai  How did you come up with the various values for the same component?Could you please assist me in this issue? If possible, a sample of the model's co...

Thank you for the reference; nevertheless, the reference links are unhelpful.

@SantoshSai , Thanks for the quick response. But I am unable login to the system/console as well. same error is throwing:-URI: /system/console.STATUS: 500MESSAGE: Server ErrorSERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-3a3f0585CAUSED BY: java.lang.IllegalArgumentException...

Robots.txt is cached at the akamai level. Akamai has updated the rules, now it is working as expected. @Anish-Sinha Thanks for the inputs.  

Apologies for the late response. We used the identical settings, but it seems to be caching someplace; we didn't find the file in the /mnt/var/www/html/content/dam/domain1/robots.txt cache folder either. We suspected that it was cached at the Akamai level, but not at the AEM level. We're collaborati...