[jira] [Commented] (SLING-6774) Allowed character set in repo init is too restrictive

["Timothee Maret (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171449#comment-16171449 ] 

Timothee Maret commented on SLING-6774:
---------------------------------------

IIUC, this issue is about extending the syntax of PATH_STRING with {{+}}, {{@}} and {{:}}.
Allowing for {{+}} and {{@}} is trivial, however I think that {{:}} is an illegal JCR character.

Thus, we should escape the {{:}} char in each path segment with
{code}
Text.escapeIllegalJcrChars(name)
{code} 

as suggested in https://wiki.apache.org/jackrabbit/EncodingAndEscaping#Escaping_paths

This means, that the bloc
{code}
set ACL for fredWilmaService
  allow jcr:write on /jcr:foo
end
{code}

would actually allow fredWilmaService to write under the path {{/jcr%3Afoo}}

Similarly, creating a path with 
{code}
create path /jcr:foo
{code}
will create a path {{/jcr%3Afoo}}

[~cziegeler] does the description above matches your expectation ?

> Allowed character set in repo init is too restrictive
> -----------------------------------------------------
>
>                 Key: SLING-6774
>                 URL: https://issues.apache.org/jira/browse/SLING-6774
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: Repoinit Parser 1.1.0
>            Reporter: Carsten Ziegeler
>            Assignee: Timothee Maret
>            Priority: Blocker
>             Fix For: Repoinit Parser 1.2.0
>
>
> As we found out in SLING-6772, the allowed character set of repoinit is too limited. We should at least add a plus and the @ sign.
> SLING-6772 as two patches for handling the @ by [~olli]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)