[jira] [Updated] (SLING-7926) JSON Content Parser should support FileVault filename escaping

["Konrad Windszus (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated SLING-7926:
-----------------------------------
    Fix Version/s:     (was: JCR ContentLoader 2.5.0)

> JSON Content Parser should support FileVault filename escaping
> --------------------------------------------------------------
>
>                 Key: SLING-7926
>                 URL: https://issues.apache.org/jira/browse/SLING-7926
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Jason E Bailey
>            Assignee: Jason E Bailey
>            Priority: Major
>
> Currently it's possible to define a json file with a name that matches a mangled namespace. Which then makes the file unable to be accessed from the ResourceResolver
> i.e. importing a file {{_jcr_content.json}} will create the node {{_jcr_content}} which cannot then be resolved as the resource resolver will attempt to convert {{_jcr_content}} to {{jcr:content}} supporting namespace mangling will additionally provide a cleaner {{colon}} support than the current recommendation of a url mangled colon of {{%3A}}.
> The exact FileVault filename escape rules are outlined at https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)