AEM Dispatcher: Resolving inaccessible content paths
This article explains how to troubleshoot and resolve cases where a specific content path is inaccessible through AEM Dispatcher, while other paths remain accessible. The solution involves reviewing dispatcher allow rules and ensuring the required content structure exists in the repository.
Description description
Environment
Adobe Experience Manager (AEM) Managed Services and AEM as a Cloud Service (AEMaaCS)
Symptoms
- A specific content path isn’t accessible through the Dispatcher, returning an error in the browser.
- Other content paths are accessible without issue.
- The issue is reproducible by navigating to the affected URLs in a browser.
Cause
The content path is inaccessible because the Dispatcher configuration doesn’t include allow rules for the path, or the content structure for the path doesn’t exist or isn’t published.
Resolution resolution
Follow the steps below to resolve the issue:
-
Review your Dispatcher configuration to ensure that allow rules for the affected content path are present and correctly set up.
-
If the allow rules are missing, update your Dispatcher configuration to include them. Deploy the updated configuration using your standard deployment process (such as Cloud Manager pipeline for AEMaaCS).
-
Validate that the content structure for the path exists in AEM and is published to the appropriate publish instance.
-
For AEMaaCS: Content structure changes must be made via code deployment (For example: using repo-init scripts or content packages in your deployment pipeline). Direct repository edits (such as using CRXDE Lite) aren’t supported in Production environments.
-
For AEM Managed Services (non-Cloud Service): If permitted, you may use CRXDE Lite to create the required folders or paths on the Author instance, then replicate as needed. Otherwise, use code deployment.
-
-
After making configuration and content changes, test access to the affected content path in a browser to confirm resolution.