Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.0RC8
Bug #8570 PROPFIND does not report lock-null resources in Filesystem class
Submitted: 2006-08-28 05:14 UTC
From: hugh at worldwebms dot com Assigned: hholzgra
Status: Closed Package: HTTP_WebDAV_Server
PHP Version: Irrelevant OS: Debian Linux
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 41 - 37 = ?

 
 [2006-08-28 05:14 UTC] hugh at worldwebms dot com (Hugh)
Description: ------------ The PROPFIND implementation in the Filesystem class which is provided with this system does not report so-called "lock-null" resources, ie. resources which do not exist yet but have been locked. This is a requirement as per the RFC (2518). The resource should return with the fields as follows: displayname - as normal creationdate - time the lock was created getlastmodifier - time the lock was created/updated resourcetype - (blank) getcontenttype - (blank) getcontentlength - 0 This issue causes problems when using later versions of Dreamweaver which try to lock the resource then issue a PROPFIND to make sure it is "there" before MKCOL is called. When PROPFIND returns forbidden, DW aborts the upload.

Comments

 [2006-10-02 10:45 UTC] hholzgra (Hartmut Holzgraefe)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.