[
https://issues.apache.org/jira/browse/SLING-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4976.
----------------------------------------
Resolution: Fixed
I have added a new WebDavDoubleSlashTest that demonstrates the difference:
* http://svn.apache.org/r1700221 is the old behavior where an URL like
/dav//test/... causes the WebDAV servlets to use the default JCR workspace
name, so such URLs are accepted for PROFIND for example, up to svn revision
1673619 (at least).
* http://svn.apache.org/r1700222 is the new behavior where the same URL causes
a 404 due to the empty JCR workspace name.
I have set fix version = JCR Webdav 2.3.2 so that this appears in that module's
release notes, although the underlying changes are probably somewhere else.
> Clarify handling of empty JCR workspace name in WebDAV URLs
> -----------------------------------------------------------
>
> Key: SLING-4976
> URL: https://issues.apache.org/jira/browse/SLING-4976
> Project: Sling
> Issue Type: Task
> Components: Servlets
> Affects Versions: JCR Webdav 2.3.0
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: JCR Webdav 2.3.2
>
>
> The handling of an empty JCR workspace name in WebDAV URLs has changed
> recently, I'll create an integration test that demonstrates the changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
