| Newsgroups |
php.pear.bugs |
| Message-ID |
<[email protected]> |
Edit report at https://pear.php.net/bugs/bug.php?id=20412&edit=1
ID: 20412
Comment by: [email protected]
Reported By: pear dot php dot net at dw-perspective dot org dot uk
Summary: Technique used is explicitly forbidden by current RFC
Status: Open
Type: Bug
Package: HTTP_WebDAV_Client
Operating System: All
Package Version: SVN
PHP Version: 5.5.16
Roadmap Versions:
New Comment:
Relevant:
https://blog.sphere.chronosempire.org.uk/2012/11/21/webdav-and-the-http-patch-nightmare
http://sabre.io/dav/http-patch/
Previous Comments:
------------------------------------------------------------------------
[2014-09-18 14:34:30] davidanderson684
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
------------------------------------------------------------------------
--
Edit this bug report at https://pear.php.net/bugs/bug.php?id=20412&edit=1