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

rajput-ankur
Community profile rajput-ankur Level 1
Job title here
Location here
3 BADGES
Level 1

Level 1

Learn more
Joined the community 10-05-2020 2:10:37 AM
Offline
Top badges earned by rajput-ankur
Customize the badges you want to showcase on your profile
Re: AEM postback gives HTTP 204 instead of HTTP 200
Avatar
Give Back 3
Level 1
rajput-ankur
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Applaud 5
View profile
rajput-ankur
- Adobe Experience Manager
I am also facing a similar kind of issue in case of SAML. When the IdP is redirecting to AEM with SAMLResponse, it is returning 204 No Content. But if I execute the same request through Postman then it is working perfectly fine. I couldn't find the request neither in request and access logs nor on Recent requests console: http://localhost:4502/system/console/requests. I even added a breakpoint on SlingMainServlet and the request is not even coming to that,

Views

337

Likes

0

Replies

1
Re: Dispatcher and Cache-Control mod_expires
Avatar
Give Back 3
Level 1
rajput-ankur
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Applaud 5
View profile
rajput-ankur
- Adobe Experience Manager
@Jörg_HohIn my case it is still not adding Cache-Control for uncacheable (denied in cache.any) request.I have usedExpiresByType application/javascript "access plus 1 month" But as soon as I add the entry to deny caching, the Cache-Control header gets removed from the final response.

Views

264

Likes

0

Replies

0
Re: iParsys-like behavior with layout containers?
Avatar
Give Back 3
Level 1
rajput-ankur
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Applaud 5
View profile
rajput-ankur
- Adobe Experience Manager
@Kautuk_shani and @om_vineet, I am not able to understand that how does this resolve the given use case?? If we keep the XF component locked on the template then the same XF will be used on all the brands and if we keep it unlocked then we have to author the XF path on all the pages. How can we solve this?

Views

581

Likes

0

Replies

0