Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-4976

Clarify handling of empty JCR workspace name in WebDAV URLs

Details

    • Task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • JCR Webdav 2.3.0
    • JCR Webdav 2.3.2
    • Servlets
    • None

    Description

      The handling of an empty JCR workspace name in WebDAV URLs has changed recently, I'll create an integration test that demonstrates the changes.

      Update: the change in behavior is apparently caused by upgrading to org.apache.felix.http.jetty/3.1.0, see SLING-4978

      Attachments

        Issue Links

          Activity

            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.

            bdelacretaz Bertrand Delacretaz added a comment - 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.

            People

              bdelacretaz Bertrand Delacretaz
              bdelacretaz Bertrand Delacretaz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: