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

Avatar

Avatar

vg_g

Avatar

vg_g

vg_g

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

ChitraMadan

MVP

Avatar

ChitraMadan

MVP

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

SureshDhulipudi

MVP

Avatar

SureshDhulipudi

MVP

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