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

Bug #13031 PEAR fails to authenticate when doing upgrade-all on non-default channel
Submitted: 2008-01-31 18:43 UTC Modified: 2008-04-10 20:19 UTC
From: timj Assigned: timj
Status: Closed Package: PEAR (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: 1.7.2    
Subscription  


 [2008-01-31 18:43 UTC] timj (Tim Jackson)
Description: ------------ This is a lot like bug #11642. If you have a non-default channel which requires HTTP authentication in order to retrieve the REST metadata, PEAR fails to use the configured username and password when doing "upgrade-all".

Comments

 [2008-01-31 20:47 UTC] timj (Tim Jackson)
Wow, what a nightmare. Had to chase this bug all the way through all the REST functions. Patch attached which seems to fix it for me; however would appreciate a sanity check before I check it in. Patch incorporates a fix to bug #13033 of necessity.
 [2008-01-31 20:47 UTC] timj (Tim Jackson)
Incidentally, the patch isn't a unified diff because of bug #13034.
 [2008-01-31 20:56 UTC] timj (Tim Jackson)
Watch out, there is a line of debugging in the patch - REST.php at the start of downloadHttp()
 [2008-01-31 21:05 UTC] timj (Tim Jackson)
Incidentally, the patch also fixes related problems like list-all etc.
 [2008-03-29 10:10 UTC] dufuz (Helgi Þormar Þorbjörnsson)
I had to look really really hard to comprehend this diff format ;-) For that matter I wrote a rather lengthy comment about this and that problem which then I managed to proof my self wrong every time. The patch looks good, basically does adds channel to all the rest functions which pass it to retrieveData which passes it to httpDownload which passes it to config get with the channel name intact Commit away IMHO
 [2008-04-10 20:19 UTC] dufuz (Helgi Þormar Þorbjörnsson)
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.