AEM 6.5 ResourceResolver is not resolving requests with path containing "_jcr_content"

Avatar

Avatar
Level 1
vg_g
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
vg_g
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
View profile
vg_g
Level 1

12-01-2021

Seeing a strange issue in one of the environments, for a request like "https://{HOST}/content/{SITE}/overview/_jcr_content/par.html", AEM is returning 404. I can see the resource "/content/{SITE}/overview/jcr:content/par.html" is available and accessible as "https://{HOST}/content/{SITE}/overview/jcr:content/par.html" .

 

My observation: ResourceResolver when mapping, it translating "jcr:content" to "_jcr_content" correctly but when its resolving it is not able to translate "_jcr_content" to "jcr:content", the process of mapping and resolving is explained here (https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#namesp...).

 

Any thoughts?

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 250
MVP
ChitraMadan
MVP

Likes

273 likes

Total Posts

165 posts

Correct reply

67 solutions
Top badges earned
Boost 250
Establish
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Boost 250
MVP
ChitraMadan
MVP

Likes

273 likes

Total Posts

165 posts

Correct reply

67 solutions
Top badges earned
Boost 250
Establish
Ignite 1
Give Back 5
Give Back 3
View profile
ChitraMadan
MVP

13-01-2021

Hi @vg_g,

 

Can you please check if the configuration "Namspace Mangling" is enabled in your configuration.

 

ChitraMadan_0-1610557981874.png

 

Answers (1)

Answers (1)

Avatar

Avatar
Ignite 1
MVP
SureshDhulipudi
MVP

Likes

163 likes

Total Posts

174 posts

Correct reply

49 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
MVP
SureshDhulipudi
MVP

Likes

163 likes

Total Posts

174 posts

Correct reply

49 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
SureshDhulipudi
MVP

12-01-2021

Is this working earlier and not working now?

If not, you have to explicitly convert to "/jcr:content" from _jcr_content in path building and do a ResourceResolver on converted path