Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15
Bug #6044 PEAR_REST::retrieveCacheFirst doesn't return error codes
Submitted: 2005-11-23 11:47 UTC
From: cweiske at cweiske dot de Assigned: cellog
Status: Closed Package: PEAR
PHP Version: Irrelevant OS: any
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 : 36 + 15 = ?

 
 [2005-11-23 11:47 UTC] cweiske at cweiske dot de
Description: ------------ When using the PEAR_REST::retrieveCacheFirst() function and an error occurs (e.g. HTTP/404), no error code is returned. That is a huge problem for frontends which can't decide what to do with the error - e.g. continue with listing the next package, or stop trying because the internet connection is down? Expected result: ---------------- $error->code !== null Actual result: -------------- $error->code === NULL

Comments

 [2006-01-02 17:53 UTC] cellog
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. now the HTTP error code is returned in the PEAR_Error