I agree, but even using the dependecy returned by depfinder,<dependency>    <artifactId>cq-dam-commons</artifactId>    <version>5.12.54</version>    <groupId>com.day.cq.dam</groupId>    <scope>provided</scope></dependency>I am getting the same exception.

Not solved in fact. After a restart, the issue comes back. Reproducible at least from 6.4.3 up to 6.5. I am suspecting that I am missing something in the templates, but not sure what yet.

Thanks, I solved by installing 6.4.4 service pack. Still not sure what in the nosamplecontent caused the issue.

Update: Issue happens using the nosamplecontent, that is the difference between the instances. I am going to setup a nosamplecontent locally to debug further.

Thanks, but we are not using the built-in Target functionality.

Additional info:AEM 6.4.3The page uses an Editable Template. I have also the same policies applied on both environments.

Hi,Does anyone know what paths are affected when requesting http://<instance>/content/mysite.targetingconfig.json URL?I have the same content and code locally and on my development server? However in the dev server I get this exception:"Unable to load targeting config for page {}".The message comes ...

28.02.2019 12:46:00.026 *WARN* [127.0.0.1 [1551375960022] GET /api/screens-dcc/devices/stati HTTP/1.1] com.adobe.granite.rest.impl.ResourceAdapterFactory Unable to handle adaptable com.adobe.cq.screens.impl.rest.DevicesStatiResourceHi, does someone know how to get rid of this message?

For example:/test -> it doesn't work/test.html -> it does workApache 2.2.15 and Dispatcher version is 4.2.2

Hi,We have redirects with Sling Mappings, but some of them are redirects without extension. Therefore the dispatcher is blocking these requests.What are recommended ways to fix this?Vanities are working fine, since I am using the vanitiy_url section. And redirects with extension as well, the extensi...