FYI @aemmarc , a colleague has confirmed that 6.5.5 does not contain the fix. He needed to reapply the hotfix over 6.5.5.

@aemmarc , if that is the case (which would be awesome, by the way!) it would be a good idea to get that details added to the SP release notes:https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/service-pack/sp-release-notes.html Thanks for the information!

@aemmarc , do you know if the hotfix will be able to be applied over 6.5.5 (I ask since 6.5.5 came out today)?

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#...

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...

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...

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/mar...