WebDAV backend can't understand 200 OK response to DELETE

Bug #1312328 reported by Oleg Artamonov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

Some WebDAV servers (e.g. Yandex.Disk) respond to DELETE with 200 OK response code instead of 204 No Content. Such response is allowed by RFC 2616 (https://tools.ietf.org/html/rfc2616#section-9.7), althought not recommended by WebDAV RFCs.

As for now duplicity WebDAV backend understands only 204 code, so it can't delete files on such servers. To fix it, in backends/webdavbackend.py

response = self.request("DELETE", url)
    if response.status == 204:

should be changed to

response = self.request("DELETE", url)
    if response.status in [200, 204]:

Changed in duplicity:
milestone: none → 0.6.24
importance: Undecided → Medium
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
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.