Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.0RC8

Bug #11816 Fatal error when locking
Submitted: 2007-08-10 22:35 UTC
From: thesaint Assigned: hholzgra
Status: Closed Package: HTTP_WebDAV_Server (version 1.0.0RC4)
PHP Version: 5.2.0 OS: Mac OS X
Roadmaps: 1.0    
Subscription  


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 : 44 + 23 = ?

 
 [2007-08-10 22:35 UTC] thesaint (Gabriel Birke)
Description: ------------ When Mac OS writes a file, it tries to lock it beforehand. It sends the LOCK command, one of the header lines is as follows: Timeout: Second-600 The code in Line 1395 expects a numeric value and crashes with a fatal error. Don't know if Mac OS X violates the standard here, but the attached patch will parse the timeout string correctly.

Comments

 [2007-11-14 11:18 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. Fault on my side probably, i expect the LOCK() handler to always overwrite the timeout property with an integer value as the Filesystem.php LOCK() does. Will now handle both string values and returned arrays. String values are trusted, they are passed on verbatim without checking. For arrays only the first timeout item will be returned