Re: [Duplicity-talk] webDAV propfind request body

[Kenneth Loafman]

Dan Muresan wrote:
> Going further with WebDAV, I found that some (well-known) DAV servers
> return nothing when <allprop> is requested. This makes duplicity think
> the archive is empty.
> 
> I believe servers returning nothing violate the spec, because <allprop>
> is supposed to return all "dead properties" and at least some live
> properties:
> 
> http://www.ietf.org/rfc/rfc4918.txt
> 
> But this is irrelevant for users... Cadaver issues a more explicit request:
> 
> <?xml version="1.0" encoding="utf-8"?>
> <propfind xmlns="DAV:"><prop>
> <getcontentlength xmlns="DAV:"/>
> <getlastmodified xmlns="DAV:"/>
> <executable xmlns="http://apache.org/dav/props/"/>
> <resourcetype xmlns="DAV:"/>
> <checked-in xmlns="DAV:"/>
> <checked-out xmlns="DAV:"/>
> </prop></propfind>
> 
> I tried this request in duplicity by modifying the variable "listbody"
> in the WebDAV backend (backends.py), and voila, collection-status and
> incremental suddenly start working on my DAV host.
> 
> Can the default request body be updated, please? Does anyone here have
> experience with WebDAV + duplicity?


Dan,

This one appears to work and does not require internet access.  Would
you try it on your target, and any others you have access to?

     <?xml version="1.0" encoding="utf-8" ?>
     <D:propfind xmlns:D="DAV:">
       <D:allprop/>
       <D:include>
         <D:supported-live-property-set/>
         <D:supported-report-set/>
       </D:include>
     </D:propfind>

...Thanks,
...Ken

signature.asc
Description: OpenPGP digital signature