But this is not what the test case in https://issues.apache.org/jira/browse/SLING-4976 <https://issues.apache.org/jira/browse/SLING-4976> validates. It now validates /dav/<valid-workspace-name>/… (which should be fine and is fine) But /dav//<valid-workspace-name/… should return the same result as for above, but in fact the // is interpreted as empty workspace name, while it should be interpreted as simple `/`, therefore it results in a 404! Konrad
> On 31 Aug 2015, at 11:49, Carsten Ziegeler <[email protected]> wrote: > > Am 31.08.15 um 11:42 schrieb Konrad Windszus: >> If I understood Carsten correctly the double slash should be accepted by the >> implementation. So IMHO the old behaviour described in SLING-4976 is the >> correct one (i.e. falling back to the default workspace). > No :) What I meant is that usually urls with a double slash are treated > as with a double slash, so > > /a//b/c is the same as /a/b/c > > Therefore if the implementation assumes that the second path element is > the workspace name, with the above urls, the name is always "b" and does > not default to anything > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
