QuestionQ14

Performance Optimization and Troubleshooting

A developer tells a DevOps engineer that a page under development renders as intended in the AEM Authoring environment but displays blank when accessed through the Dispatchers.

No errors appear in the browser console.

Other pages using this page template render correctly.

The page renders correctly through the www URL, but displays blank through the non-www URL.

What is the cause of this issue?

  • A The 'anonymous' user does not have read permissions on the path.
  • B The domain's IP is not listed in the /allowedClients section.
  • C A matching entry is missing in the /virtualhost section.
  • D There is an incorrect rule in the /filter section.
Explanation

AEM Dispatcher chooses a farm by matching the incoming request’s host, URI, and scheme against its /virtualhosts configuration. If the www hostname is configured but the non-www hostname is not, requests to the non-www address do not select the intended farm and can be handled by an incorrect fallback configuration, producing a blank page. Each supported domain hostname requires a matching /virtualhosts entry.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!