Bug #36947 [Opn->Fbk]: HTTP stream wrapper does not treat all 2xx status codes as successful

Edit report at https://bugs.php.net/bug.php?id=36947&edit=1 ID: 36947 Updated by: ajf@php.net Reported by: Jared dot Williams1 at ntlworld dot com Summary: HTTP stream wrapper does not treat all 2xx status codes as successful -Status: Open +Status: Feedback Type: Bug Package: Streams related Operating System: Win2000 PHP Version: 5.1.3RC2 Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2014-04-11 22:37:01] neufeind@php.net So? Fixed (and close this) or not? ------------------------------------------------------------------------ [2012-06-28 00:51:54] pollita@php.net Could you elaborate on "not fixed" (preferably with a repro case)? The code added by Mike in 2008 seems pretty liberal: /* all status codes in the 2xx range are defined by the specification as successful; * all status codes in the 3xx range are for redirection, and so also should never * fail */ if (response_code >= 200 && response_code < 400) { reqok = 1; ------------------------------------------------------------------------ [2012-02-01 05:46:56] josh at joshbutts dot com This does not appear to be fixed in 5.3.6 compiled from source on Mac OS 10.7 ------------------------------------------------------------------------ [2008-10-27 11:59:01] bjori@php.net Fixed in PHP5.3, but I don't think it has been documented properly yet. See: http://php.markmail.org/message/5rockhlt6hj7tzrb ------------------------------------------------------------------------ [2006-04-02 13:39:17] Jared dot Williams1 at ntlworld dot com Was raised on php internals ~year ago.. http://marc.theaimsgroup.com/?l=php-dev&m=111383344601864&w=2 http://marc.theaimsgroup.com/?l=php-dev&m=111384113712112&w=2 http://marc.theaimsgroup.com/?l=php-dev&m=111384249807034&w=2 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=36947 -- Edit this bug report at https://bugs.php.net/bug.php?id=36947&edit=1