Re: [Duplicity-talk] webDAV propfind request body

[Dan Muresan]

> It sounds like we just need a list of <prop>s that are needed by
> duplicity and forget about the rest.  Those should be standard.

Yes -- but if I remember the code correctly, duplicity doesn't require
any properties in particular; it just uses <propfind> to list the files
in the web folder. Any property that the server understands would do.

My patch (based on a Cadaver captured request, and thus based on
libneon) just lists some commonly available properties:

<getcontentlength xmlns="DAV:"/>
<getlastmodified xmlns="DAV:"/>
<resourcetype xmlns="DAV:"/>
<checked-in xmlns="DAV:"/>
<checked-out xmlns="DAV:"/>

(whether the xmlns is inherited or listed explicitly does not seem to
make a difference, and I don't know which one is safer; I suspect
Cadaver, which uses libneon, is again a good reference)

-- Dan