AEM 6.5 ResourceResolver is not resolving requests with path containing "_jcr_content" | Community
Skip to main content
V
vg_g
New Member
January 12, 2021
Solved

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

  • January 12, 2021
  • 2 replies
  • 2968 views

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#namespace-mangling).

 

Any thoughts?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ChitraMadan

Hi @vg_g,

 

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

 

 

2 replies

SureshDhulipudi
Community Advisor
SureshDhulipudiCommunity Advisor
Community Advisor
January 13, 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

    V
    vg_gAuthor
    New Member
    January 13, 2021
    thanks for your response. It was working correctly until last week in publish, in author its working correctly even now.
    ChitraMadan
    Community Advisor
    ChitraMadanCommunity AdvisorAccepted solution
    Community Advisor
    January 13, 2021

    Hi @vg_g,

     

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

     

     

      V
      vg_gAuthor
      New Member
      January 19, 2021
      Thanks @ChitraMada, I could see it's disabled.
      Terms & ConditionsAccessibility statement

      Loading footer...