This is the namespace mangling feature in the Sling Resource Resolver Factory configuration:
Namespace Mangling Defines whether namespace prefixes of resource names inside the path (e.g. "jcr:" in "/home/path/jcr:content") are mangled or not. Mangling means that any namespace prefix contained in the path is replaced as per the generic substitution pattern "/([^:]+):/_$1_/" when calling the "map" method of the resource resolver. Likewise the "resolve" methods will unmangle such namespace prefixes according to the substituation pattern "/_([^_]+)_/$1:/". This feature is provided since there may be systems out there in the wild which cannot cope with URLs containing colons, even though they are perfectly valid characters in the path part of URI references with a scheme. The default value of this property if no configuration is provided is "true". (resource.resolver.manglenamespaces) As indicated in the description, the option is on by default, so turning it off should fix your issue here. This is a feature that is meant for JCR namespaces appearing in paths, as they are prefixed by colons, such as "jcr:content" getting mangled into "_jcr_content" that is often seen in AEM content trees. As such, you may need to validate that turning this off isn't going to cause other issues in return. On Tue, Aug 9, 2016 at 10:37 PM, Christopher Rockwell <cmroc...@umich.edu> wrote: > Hi all. > > I’m having trouble with outbound links within AEM containing colons (:) > within the URL hash. The problem seems to stem from Sling URL mangling. I > created a Stackoverflow question with the details- see link below. I’m hoping > folks on the list can take a look and provide some suggestions. > > http://stackoverflow.com/questions/38752586/outbound-links-with-colon-in-hash-get-mangled > > <http://stackoverflow.com/questions/38752586/outbound-links-with-colon-in-hash-get-mangled> > > Thanks! > Chris Rockwell > University of Michigan > Web Services, Sr. Application Developer > cmroc...@umich.edu <mailto:cmroc...@umich.edu>, > >
