Re: [Duplicity-talk] Does duplicity rely on a special namespace abbreviation in webdav respones?

[edgar . soldin]

hey Felix,

see inline

On 19.07.2022 08:51, Felix Prüter via Duplicity-talk wrote:
> Hi,
> I use duplicity 0.7.19.

duplicity is outdated and  not maintained any more. please upgrade to latest 
0.8.23 and see if the error persists.

> Full and incremental backups to a webdav server responding with <D:multistatus 
> xmlns:D="DAV:">(...) work.
> Full backups to a webdav server responding with <ns0:multistatus 
> xmlns:ns0="DAV:">(...) work as well.
> BUT incremental backups to a webdav server responding with <ns0:multistatus 
> xmlns:ns0="DAV:">(...) does NOT work.
> Snippet from the log:
> WebDAV PROPFIND /seafdav/mail7/mail7-tmp/ request2 with headers: {'Connection': 
> 'keep-alive', 'Depth': '1', 'Authorization': 'Basic dGl0dXN...lFVUDRSTw=='}
> WebDAV data length: 95
> WebDAV response2 status 207 with reason 'Multi-Status'.
> Last full backup date: none

that's not enough information. run duplicity with max. verbosity '-v9' and 
pastebin the full error stack, remove information you deem private in it first.

> Does the webdav backend require a "d" as abbreviation for the xml namespace and 
> does not parse the xml response otherwise?

can't tell, but feel free to have a look in
 
https://gitlab.com/duplicity/duplicity/-/blob/main/duplicity/backends/webdavbackend.py

alternatively you may try to use lftp+webdav[s]:// or rclone:// backend 
instead, both support webdav. check the manpage 
https://duplicity.us/vers8/duplicity.1.html on how to set them up.

good luck! ..ede/duply.net