Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

brijesht7477132
brijesht7477132
Online

Badges

Badges
13

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
12

Posts & Comments

Posts & Comments
17

Discussions

Discussions
0

Questions

Questions
1

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by brijesht7477132
Customize the badges you want to showcase on your profile
Re: Asset HTTP json is not cachable in dispatcher docroot - Adobe Experience Manager Headless 04-07-2022
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 Filter --> Dispatcher --> Client(Browser) Hoping this will solve your problem

Views

88

Likes

2

Replies

1
Re: Asset HTTP json is not cachable in dispatcher docroot - Adobe Experience Manager Headless 30-06-2022
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 response is ready to send from publisher to webserver (for reference: https://www.codejava.net/java-ee/servlet/how-to-create-java-servlet-filter)Hoping it will be of some use for you

Views

208

Likes

2

Replies

3
Re: GSON version update to 2.8.9 issue - Adobe Experience Manager 28-06-2022
Hi @SantoshSai : Thank you for your time and comments

Views

67

Likes

2

Replies

0
Re: GSON version update to 2.8.9 issue - Adobe Experience Manager 28-06-2022
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 case it is picking the version 2.8.2.I fixed it by simply changing the order of including dependency where Gson dependency is included first and after that Uber Jar dependency. Showing sample below. That...

Views

68

Likes

2

Replies

0
Re: GSON version update to 2.8.9 issue - Adobe Experience Manager 27-06-2022
@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 vulnerability is removed it is started failing. Gson gson = new GsonBuilder().disableHtmlEscaping().create();

Views

90

Like

1

Replies

2
GSON version update to 2.8.9 issue - Adobe Experience Manager 27-06-2022
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 also updated the Junit version from 4.12.0 to 4.13.2 as suggested in maven.Post update of Gson version the code is compiling fine, but Junit test cases are started failing with the below exception. Till...

Views

106

Likes

0

Replies

5
Re: Experience Fragment HTML structure - Adobe Experience Manager 08-01-2019
Hi, We need experience fragment only as we need to maintain structure which we cannot achieve using content fragment.

Views

6.8K

Likes

0

Replies

0
Re: Experience Fragment HTML structure - Adobe Experience Manager 08-01-2019
Hi Gaurav, Thanks for the reply. We did try Decoration properties but that makes component non editable in author mode. So not usefully for us.

Views

6.8K

Likes

0

Replies

1
Experience Fragment HTML structure - Adobe Experience Manager 06-01-2019
Hi All,Our application is SPA. We are sharing content from AEM to Angular to display it in front end. We author our content using the Experience Fragment and when we are sharing our experience fragment HTML structural is added with additional div and classes. Attaching the HTML structure below. The first two div are the additional div. These additional div breaking the HTML structure in Angular end as the CSS and JS are written depending on the actual HTML structure which is not including these ...

Views

7.2K

Likes

0

Replies

6
Editable Template AEM 6.4 - Adobe Experience Manager 16-09-2018
Hi All,I am facing one issue that while creating Editable template and editing it how to include initial content in my template. I followed the same steps mentioned in few articles over net. I tried copy pasting initial node from section page template of we-retail to my template but it didn't work. can someone help me to include initial content.Second is the observation that suppose i have initial content in my editable template using that i created few page. Later i added few component in my in...

Views

1.2K

Likes

0

Replies

1