[#5664] RPC/WebDAV does not pass full path for DELETE
Summary RPC/WebDAV does not pass full path for DELETE
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners jan@horde.org
Requester bklang@horde.org
Created 2007-08-23 (5179 days ago)
Due
Updated 2007-11-18 (5092 days ago)
Assigned 2007-10-22 (5119 days ago)
Resolved 2007-11-18 (5092 days ago)
Milestone
Patch Yes

Comments
Ben Klang <bklang@horde.org> 2007-08-23 18:35:44
The DELETE method within the RPC/webdav.php object does not properly 
pass the full path to the called function, as do PUT and BROWSE.  This 
prevents the called module from being able to determine the proper 
collection for the object being deleted.  This patch changes the API 
call to pass the full path including the collection rather than just 
the name of the object, to match the behavior of the other 
RPC/webdav.php methods.

Jan Schneider <jan@horde.org> 2007-09-18 23:54:50
Unfortunately it's not that easy. DELETE is completely broken at the 
moment, and I doubt it ever worked. the _*_delete() methods in the 
applications' apis have been added for syncml support and expect the 
object's uid. We don't have that uid in the webdav interface at all, 
instead we identify object by the path, including the internal id.

Ben Klang <bklang@horde.org> 2007-10-22 15:24:27
Fix committed to HEAD.  For the record, the API method was renamed to 
path_delete() within the applications.  This is what the WebDAV RPC 
driver calls to make deletes within applications.  This avoids SyncML 
conflicts.

Jan Schneider <jan@horde.org> 2007-10-22 15:51:25
Still has to be fixed/implemented for the other apps.