Re: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning

2007-11-02 Thread Alexey Zakhlestin
On 11/2/07, Jared Williams [EMAIL PROTECTED] wrote: Yes, had fun with trying to use http php streams ... Imo, 2xx status codes should always be considered succesful. I believe, that there should be possibility to get even the document with 404th status (as the error-page might be valuable

RE: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning

2007-11-02 Thread Jared Williams
November 2007 23:10 To: PHP Internals Subject: Re: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning This is probably better: if (options STREAM_ONLY_GET_HEADERS || (php_stream_context_get_option(context, http, ignore_errors, tmpzval) == SUCCESS

Re: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning

2007-11-02 Thread David Coallier
they are. http://bugs.php.net/bug.php?id=36947 http://marc.info/?l=php-internalsm=111384113712112w=2 J -Original Message- From: David Zülke [mailto:[EMAIL PROTECTED] Sent: 01 November 2007 23:10 To: PHP Internals Subject: Re: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any

[PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning

2007-11-01 Thread David Zülke
Hi folks, I've recently played with CouchDB, which is a document database with a RESTful HTTP interface. I noticed, however, that there is no way to prevent PHP from throwing a warning on response codes other than 200, 206, 301, 302 and 303. Something like 201 Created throws a warning,

Re: [PHP-DEV] [Patch] http_fopen_wrapper.c and allowing any response code w/o warning

2007-11-01 Thread David Zülke
This is probably better: if (options STREAM_ONLY_GET_HEADERS || (php_stream_context_get_option(context, http, ignore_errors, tmpzval) == SUCCESS Z_BVAL_PP(tmpzval))) { - David Am 02.11.2007 um 00:06 schrieb David Zülke: Hi folks, I've recently played with CouchDB, which is a