Hi @babusankar , Here is the catch you have to update pragna header after the filterChain.doFilter(); method.Meaning you are updating the header after the request is process.Th flow should be Client(Browser) --> Dispatcher --> Java Servlet Filter --> AEM OOTB Servlet/Filter/Service --> Java Servlet ...

Hi @babusankar : Sorry by mistake I pressed the button me too. I am not having this issue.It Pragma header will be causing this issue. You can raise this issue with Adobe but as a workaround, you can create a Java Servlet filter and put conditions for the asset API remove this Pragma header once the...

Hi @SantoshSai : Thank you for your time and comments

Hi @SantoshSai , I figured out what is causing the issue. It's the AEM Uber Jar. Things are working fine until I added the Uber Jar dependency. We are using AEM 6.4.8 version and it seems that the Uber jar version 6.4.8 using Gson transitive dependency of 2.8.2 version and while running the test cas...

@SantoshSai : Thank you for the response. But we are using the Gson object as a method local variable, not as a class-level variable, the line which we used to create Gson object is mentioned below.Just to add it is working till version 2.8.8 but as soon as make it 2.8.9 version from where the vulne...

Hi All, We are using Gson in our AEM code repository but below Gson version 2.8.9 it has a security vulnerability. To fix this we should increase the Gson maven version equal or greater than 2.8.9.In our AEM code repository we tried updating the gson version from 2.8.0 to 2.8.9 along with that we al...

Hi, We need experience fragment only as we need to maintain structure which we cannot achieve using content fragment.