[
https://issues.apache.org/jira/browse/SLING-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-765.
-----------------------------------
Resolution: Fixed
Implemented this change in Rev. 725038.
> Namespace mangling in the new ResourceResolver should be enabled by default
> ---------------------------------------------------------------------------
>
> Key: SLING-765
> URL: https://issues.apache.org/jira/browse/SLING-765
> Project: Sling
> Issue Type: Improvement
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> The new Resource Resolver (JcrResourceResolver2) supports namespace mangling
> to prevent JCR paths containing colons, that is namespace prefixed names),
> being used in URLs.
> Upon ResourceResolver.map, any prefix: is converted to _prefix_ while on
> ResourceResolver.resolver any mangled _prefix_ is converted to a real
> prefix:. This reverse mangling vom _prefix_ to prefix: is only applied if
> prefix is really a registered namespace prefix. otherwise the _prefix_
> remains unmodified.
> Currently this namespace mangling is disabled by default. Now there are not
> only usecases with applications out in the wild having issues with colons in
> the path part of URLs, there are also real issues with client browsers if
> prefixed names are used as relative URLs. In this case browsers may assume
> the prefix not as part of the relative path but as an absolute URI where the
> prefix is the scheme name, which of course would fail the application.
> Therefore, the default value for namespace mangling should be changed to
> "enabled".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
