http://pear.php.net/bugs/search.php?cmd=display&package_name%5B0%5D=HTTP_WebDAV_Client Search Results en-us pear-webmaster@lists.php.net pear-webmaster@lists.php.net hourly 1 2000-01-01T12:00+00:00 http://pear.php.net/gifs/pearsmall.gif http://pear.php.net/bugs http://pear.php.net/bugs/20412 HTTP_WebDAV_Client Bug Reported by davidanderson684 2014-09-18T18:34:30+00:00 PHP: 5.5.16 OS: All Package Version: SVN 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]]> HTTP_WebDAV_Client Bug Reported by davidanderson684 2014-09-18T18:34:30+00:00 PHP: 5.5.16 OS: All Package Version: SVN 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]]> 2014-09-18T18:34:30+00:00 pear dot php dot net at dw-perspective dot org dot uk HTTP_WebDAV_Client Bug