You might as well add these as well while you are there. I put all mine in a new /conf.d/rewrites/mod_locationmatch.rules file --<LocationMatch "\.(?i:xml)$"> ForceType text/xml Header set Content-Disposition inline </LocationMatch><LocationMatch "\.(?:gif|jpe?g|png)$"> ForceType...

Ok, so I found that apparently is an expected log entry, and so the alert was downgraded from warn to debug in August 2019. https://issues.apache.org/jira/browse/SLING-8637 

That is most likely a red herring; a false lead. It is just likely another instance of the same error. I say this from 3-4 years experience in living with this error on just about every GET request that has anything to do with the editable templates. It is still happening in 6.5.3 too. Same error (p...

Several Core Components come with client libraries that need to be included on the page in order for the component to function properly.