AEM Dispatcher: Resolving intermittent page and asset loading issues caused by unwhitelisted CDN domains
This article explains how to resolve intermittent page loading and asset delivery issues in Adobe Experience Manager (AEM) Dispatcher that occur when a new CDN domain isn’t whitelisted in the dispatcher configuration.
Description description
When a new CDN domain is introduced in your environment, requests from that domain can blocked by AEM Dispatcher if the domain isn’t included in the allowed list. This can result in intermittent failures when accessing site pages or loading assets. The issue affects any AEM environment where dispatcher filtering is used to control allowed client domains.
Environment
Adobe Experience Manager (AEM), all versions using Dispatcher.
Symptoms
- Intermittent failures when accessing live site pages
- Asset delivery problems for end users
Cause
The new CDN domain wasn’t added to the dispatcher configuration’s whitelist, causing requests from the CDN to be blocked or inconsistently processed.
Resolution resolution
Follow the steps below to resolve the issue:
- Identify the new CDN domain that needs to be whitelisted (For example:
cdn.example.com). - Access the configuration files for each affected dispatcher instance. The relevant file is typically named
dispatcher.anyor may be a custom include file for allowed hosts. - Locate the section that defines allowed hosts or domains (such as
/allowedClientsor/filterrules). - Add an entry to whitelist the new CDN domain (For example: add
cdn.example.comto the allowed list). - Save the configuration file, and reload or restart the dispatcher service to apply the changes.
- Verify that the CDN domain is now accepted by the dispatcher by accessing site pages and confirming that assets load correctly.