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 (at) horde (dot) org |
Requester | bklang (at) horde (dot) org |
Created | 08/23/2007 (6509 days ago) |
Due | |
Updated | 11/18/2007 (6422 days ago) |
Assigned | 10/22/2007 (6449 days ago) |
Resolved | 11/18/2007 (6422 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | Yes |
State ⇒ Assigned
State ⇒ Resolved
path_delete() within the applications. This is what the WebDAV RPC
driver calls to make deletes within applications. This avoids SyncML
conflicts.
State ⇒ Feedback
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.
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ RPC/WebDAV does not pass full path for DELETE
Queue ⇒ Horde Framework Packages
New Attachment: RPC-delete-path-fix.diff
State ⇒ Unconfirmed
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.