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

Bug #10690 RunTest.php parses HTTP headers for non-CGI tests
Submitted: 2007-04-11 21:23 UTC
From: jstump Assigned: jstump
Status: Closed Package: PEAR (version 1.5.2)
PHP Version: 5.2.0 OS: All
Roadmaps: 1.5.3    

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:
Solve the problem : 30 - 30 = ?

 [2007-04-11 21:23 UTC] jstump (Joe Stump)
Description: ------------ When you specify --cgi=/path/to/php-cgi RunTest.php parses the output expecting headers, even if the cgi wasn't used the execute the code. The problem with this is that output that matches "Foo\n\nBar" will get munged in the header checking around line 512 of RunTest.php. Expected result: ---------------- You shouldn't check for headers or munge the output if the binary from --cgi wasn't actually used (the only time it's used is if --GET--, --POST--, etc. are actually specified). Actual result: -------------- It nukes the first line of a double spaced output.


 [2007-04-12 01:54 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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.