Just a quick addendum for those who are searching for this. Since Dispatcher 4.1.11, response headers can now be cached by the dispatcher and served when requesting cached items. See https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#caching-http-response-headers for more information.

This can be done with normal path-based ACLs, but you need to allow more than just access to cq:annotations.EDIT: I forgot to mention, the permissions below are on the /content node as allow with jcr:read & rep:write base permissions, and restrictions based on the lists below.You need to allow write for the following rep:globs/*/cq:annotations/*/cq:annotations/*You also need to allow write for the following rep:itemNamescq:lastModifiedcq:lastModifiedByI also added these rep:itemNames for good me...

I appreciate the help, Steve. Hopefully you are able to look further than the public dependencies in Adobe's Nexus repo. I tested against all 6.1 variants (6.1.0, 6.1.0-SP1, and 6.1.0-SP1-B0001) and all fail with the same verification error.Saying you are Java 8 compatible and not letting developers use Java 8 is like Microsoft saying "Excel runs on Windows 10, but if you want to use formulas, you need to use windows XP". I do understand that you can get the unobfuscated jar, but my current clie...

smacdonald2008 wrote... [Workaround]:- As a test - try using JDK 7 - lets see if its a JDK issue. Let us know what happens. Please open a ticket on this. If there is a bug - you need to report this to support so it can move up the chain to Eng team so it can be fixed. https://helpx.adobe.com/marketing-cloud/contact-support.html TBH, that isn't really a reasonable approach. The documentation says that Java 8 is supported (https://docs.adobe.com/docs/en/aem/6-1/deploy/technical-requirements.html#J...