[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-talk] webDAV propfind request body
From: |
Dan Muresan |
Subject: |
[Duplicity-talk] webDAV propfind request body |
Date: |
Mon, 09 Jun 2008 19:45:38 +0300 |
User-agent: |
Thunderbird 2.0.0.14 (X11/20080505) |
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
- [Duplicity-talk] webDAV propfind request body,
Dan Muresan <=