WebDAV PROPFIND response violates XML-Namespace

Bug #1420673 reported by Dieter Maurer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Undecided
Unassigned

Bug Description

Zope 2.13.19

Issuing a WebDAV "PROPFIND" againt a Plone "Folder", I got a response violationg XML-Namespace:

<?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:">
<d:response>
<d:href>/partner/bp3/test/</d:href>
<d:propstat xmlns:n="http://www.zope.org/propsets/default">
  <d:prop>
  <n:title>Test</n:title>
  </d:prop>
  <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat xmlns:n="DAV:">
  <d:prop>
  <n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
 ...
  </d:prop>
  ...
</d:propstat>
</d:response>
...
</d:multistatus>

The namespace prefix inside the second "propstat" is not defined.

Tags: webdav
Dieter Maurer (d.maurer)
affects: acquisition → zope2
Revision history for this message
Tres Seaver (tseaver) wrote :

Looks to me like the 'n:' prefix is associated with the 'DAV:' namespace in the second '<d:propstat>' element. If I take your example and drop the ellipses, xmllint is happy::

    $ xmllint /tmp/lp1420673.xml
    <?xml version="1.0" encoding="utf-8"?>
    <d:multistatus xmlns:d="DAV:">
    <d:response>
    <d:href>/partner/bp3/test/</d:href>
    <d:propstat xmlns:n="http://www.zope.org/propsets/default">
    <d:prop>
    <n:title>Test</n:title>
    </d:prop>
    <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
    <d:propstat xmlns:n="DAV:">
    <d:prop>
    <n:creationdate>1970-01-01T12:00:00Z</n:creationdate>
    </d:prop>
    </d:propstat>
    </d:response>
    </d:multistatus>

Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.