Re: Resource name restrictions

2025-05-30 Thread Konrad Windszus
And even in the PostServlet we only generate compliant names in case the name is not explicitly given in the parameter: https://github.com/apache/sling-org-apache-sling-servlets-post/blob/7ff7280c7ba89592186ac76d33b481d73abba323/src/main/java/org/apache/sling/servlets/post/impl/operations/Abstrac

Re: Resource name restrictions

2025-05-30 Thread Carsten Ziegeler
Hi Konrad, true, I thought we had something in the providers, but it is actually in the POST servlet - which covers only one way of creating resources. Regards Carsten On 30.05.2025 11:59, Konrad Windszus wrote: Hi Carsten, Thanks for your comments. Regarding: I don't think that a general

Re: Resource name restrictions

2025-05-30 Thread Konrad Windszus
Hi Carsten, Thanks for your comments. Regarding: > I don't think that a general escaping method helps as providers usually do > their own escaping already today. I don’t think this is true, e.g. for the most popular JCR Resource Provider. It just bails out currently with an exception for non-JC

Re: Resource name restrictions

2025-05-29 Thread Carsten Ziegeler
Hi, those two rules sound reasonable and is probably the only check that the resource resolver itself could do. I don't think that a general escaping method helps as providers usually do their own escaping already today. If these providers do not switch to the general one, it does not help.