The Dispatcher has been Adobe's/CQs standard Load Balancer. Not sure why you say you've never seen it as an LB @Jörg_Hoh It's like in the front of the documentation and what Adobe has recommended from the start beginning with CQ5 https://experienceleague.adobe.com/en/docs/experience-manager-dispatch...

AEM does not allow us to use the JSON extension.We always have to use it on jcr:content.custom.jsonwhen the extension is .html we can hit the page directly but if its anything other than that we have to hit jcr:content Any clues as to why it behaves this way ?

Which users you added?what permissions were give. I have exact same issue.

@ManviSharma Correct. How do we avoid this? Can we avoid it?Why hasn't it been fixed yet? I am using the xml style of OSGi configuration will there be any difference if I use the JSON style OSGi configuration. i.e. the one that is deployed as a JSON file.{"resource.resolver.mapping": ["/content/aem-...

There is an OSGi configuration called org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl. Here we specify the /etc/map path url shortening etc. If we open this file, make a change and save it. Either by Felix Console, Incoming Content Package via Package Manager or via CRXDE Lite....

Did you get a solution to this? I am currently facing the same issue right now