Validation and Debugging using the Dispatcher Tools

The Dispatcher tools are used to validate and debug your project’s Dispatcher configuration. Learn more about how to use those tools in the pages referenced below, based on whether your project’s Dispatcher configuration is structured in flexible mode or legacy mode:

  • Flexible mode - the recommended mode, and the default for AEM archetype 28 and higher, which is also used by Cloud Manager for new environments created after the Cloud Manager 2021.7.0 release. Customers can activate this mode by adding the folder and file opt-in/USE_SOURCES_DIRECTLY. By using this more flexible mode, there are no limitations in the file structure under the rewrites folder that in legacy mode required a single rewrite.rules file. Also, there is no limitation on the number of rules you can add. For details on folder structure and local validation, see Validating and Debugging using Dispatcher Tools.

  • Legacy mode - for details on the folder structure and local validation for Dispatcher configuration legacy mode, see Validating and Debugging using Dispatcher Tools (Legacy)

For more information on how to migrate from the legacy configuration model to the more flexible one, provided with AEM archetype 28 onwards, see this documentation.

Content Disposition

For the publish tier, the default for serving blobs is as an attachment. Override this setting using the standard content disposition header in the Dispatcher.

Below is an example of how the configuration should look like:

<LocationMatch "^\/content\/dam.*\.(pdf).*">
 Header unset Content-Disposition
 Header set Content-Disposition inline
</LocationMatch>