Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39185 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19916 invoked from network); 22 Jul 2008 13:48:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2008 13:48:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=nfontes@cynigram.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nfontes@cynigram.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain cynigram.com designates 66.249.92.173 as permitted sender) X-PHP-List-Original-Sender: nfontes@cynigram.com X-Host-Fingerprint: 66.249.92.173 ug-out-1314.google.com Received: from [66.249.92.173] ([66.249.92.173:62452] helo=ug-out-1314.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/4E-46193-335E5884 for ; Tue, 22 Jul 2008 09:48:37 -0400 Received: by ug-out-1314.google.com with SMTP id h3so385287ugf.29 for ; Tue, 22 Jul 2008 06:48:33 -0700 (PDT) Received: by 10.67.10.8 with SMTP id n8mr2548148ugi.23.1216734511972; Tue, 22 Jul 2008 06:48:31 -0700 (PDT) Received: from ?10.224.251.3? ( [85.183.90.3]) by mx.google.com with ESMTPS id w40sm2561494ugc.5.2008.07.22.06.48.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jul 2008 06:48:05 -0700 (PDT) Message-ID: <4885E513.6080702@bitextender.com> Date: Tue, 22 Jul 2008 15:48:03 +0200 Organization: Bitextender GmbH User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: internals@lists.php.net X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: Noah Fontes Subject: Patch for HTTP successful status codes From: noah.fontes@bitextender.com (Noah Fontes) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, The HTTP wrapper currently only accepts status codes 200 and 206 as successful in the 2xx range. Response codes like 202 (Accepted) fail and throw a warning. However, the HTTP specification defines all 2xx status codes as successful. This has posed some problems for us in writing RESTful applications effectively, as we're trying to take advantage of the full spectrum of successful codes. The patch to fix this problem is relatively straightforward; see http://cynigram.com/~nfontes/http_fopen_wrapper.patch If anyone could take a look at this, I would be most grateful. Thanks and regards, Noah - -- Noah Fontes Bitextender http://www.bitextender.com/ Phone: +1 919 349 9826 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIheUThitK+HuUQJQRArGfAKCJsEZ8QDFcWpoI4g2ZsbzGVsCAxgCgtZEk 7S66/HWfSf16D2FxUTMVsGU= =zalu -----END PGP SIGNATURE-----