WebDAV Issue Collection #268

voroyam · 2018-07-12T13:47:44Z

WebDAV Issue Collection

Document required HTTP/WebDAV methods (in FAQ?)

@michaelstingl

owncloud-archive/documentation#2753

Today, a user asked me about the HTTP/WebDAV methods ownCloud uses. Could we document it somewhere?

This are the answers I've got from my colleagues:

@davivel

mobile clients use PROPFIND, MKCOL, COPY & MOVE from that list

@guruz

same for desktop.. normal webdav clients are supposed to use OPTIONS too

@davivel

besides of HTTP: GET, PUT, POST, DELETE ; we also use HEAD sometimes
New Messages

@PVince81

also REPORT
DELETE, PUT, POST

00006724

if ($request_method !~ ^(DELETE|PROPFIND|PUT|GET|HEAD|POST|OPTIONS|REPORT|MKCOL|MOVE|PROPPATCH|COPY|PATCH)$ ) {
return 405;
}

https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md

Any suggestions on where best to put this documentation?

Developer docs, but not sure where. Maybe a new section about HTTP APIs ?

could be something similar / close to the OCS Share API page

Document new DAV endpoint and sub-endpoints

@PVince81

owncloud-archive/documentation#2224

@DeepDiver1975

One way to discover the available endpoints is by doing a PROPFIND on "remote.php/dav" or using cadaver on that URL.

@PVince81 Something for #2074 ?

Probably should also include #2120 so the older issue could be closed?

Yeah, should include #2120 and any others

Describe cryptic error message during failed uploads

@ghost

owncloud-archive/documentation#2145

Another cryptic error message was introduced with owncloud/core#20927 (Stable8.1+):

Error while copying file to target location (copied bytes: xxx, expected filesize: yyy)

This could show up during uploads in addition to the existing dreaded:

Sabre_DAV_Exception_BadRequest: expected filesize xxx got yyy

Both are not described anywhere and a lot of people are struggling with those message and their meaning. For the second message i've collected some reasons in owncloud/core#9832 (comment). No idea if one of those are now replaced by the new message.

For the new error:

streamCopy here is used at the moment where the data is read from the PHP Input and copied into a part file on the target storage. If the target storage is not local (ex: FTP) and that storage is slow / not available / broken, it is likely that streamCopy will fail either at the beginning, or in the middle of the copy.

In this case, the issue is most likely due to the target storage and not the client<->server connection.

from owncloud/core#20927 (comment)

From @PVince81:

There is one valid case where streamCopy would not return all bytes, that's when the quota is reached. But the it will also return false.

Other failures could be when writing to external storage but the connection took too long to respond, or the network connection to the ext storage is flaky.