Description: ------------ The June 2014 RFC (http://tools.ietf.org/html/rfc7231#section-4.3.4) for HTTP states: "An origin server that allows PUT on a given target resource MUST send a 400 (Bad Request) response to a PUT request that contains a Content-Range header field (Section 4.2 of [RFC7233]), since the payload is likely to be partial content that has been mistakenly PUT as a full representation. Partial content updates are possible by targeting a separately identified resource with state that overlaps a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for example, the PATCH method defined in [RFC5789])." The current HTTP_WebDav_Client uses *only* this forbidden method. So, it can't work with compliant servers. One example of a server implementing this correctly: https://github.com/owncloud/core/issues/10386

Relevant: https://blog.sphere.chronosempire.org.uk/2012/11/21/webdav-and-the-http-patch-nightmare http://sabre.io/dav/http-patch/