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

SOLVED

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

Avatar

Level 1

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @vg_g,

 

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

 

ChitraMadan_0-1610557981874.png

 

View solution in original post

5 Replies

Avatar

Community Advisor

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

Avatar

Level 1
thanks for your response. It was working correctly until last week in publish, in author its working correctly even now.

Avatar

Community Advisor
Can you check the Resource Resolver Factory configuration - Compare with working vs not working

Avatar

Correct answer by
Community Advisor

Hi @vg_g,

 

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

 

ChitraMadan_0-1610557981874.png