Noah Fontes wrote:
I think PHP implicitly follows any Location headers it can. That's
probably not the right behavior, but for an automated process it's not bad.
It's a configurable option (don't have the code in front of me, so no
proof, sorry). You can set redirects = 0, and have http not
Edward Z. Yang wrote:
It's a configurable option (don't have the code in front of me, so no
proof, sorry). You can set redirects = 0, and have http not follow any
redirects.
Whoops, I'm talking about pecl/http, not the http wrapper. Disregard the
above.
--
Edward Z. Yang
Am 25.07.2008 um 12:53 schrieb Hannes Magnusson:
I think changing all 3xx status codes to be success is a slightly more
bc break then you think.
A simple example:
I do a file_get_contents() request. Store it in a local buffer.
I do a second file_get_contents(), get a error (304) back, print
On Sat, Jul 26, 2008 at 22:37, David Zülke [EMAIL PROTECTED] wrote:
Am 25.07.2008 um 12:53 schrieb Hannes Magnusson:
I think changing all 3xx status codes to be success is a slightly more
bc break then you think.
A simple example:
I do a file_get_contents() request. Store it in a local
Am 26.07.2008 um 22:53 schrieb Hannes Magnusson:
On Sat, Jul 26, 2008 at 22:37, David Zülke [EMAIL PROTECTED]
wrote:
Am 25.07.2008 um 12:53 schrieb Hannes Magnusson:
I think changing all 3xx status codes to be success is a slightly
more
bc break then you think.
A simple example:
I do a
Did you yet? :)
Am 24.07.2008 um 14:42 schrieb Michael Wallner:
David Zülke wrote:
So... who's gonna commit it? :)
I'll commit in the next few hours if nobody objects.
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 25.07.2008, at 12:34, David Zülke wrote:
Did you yet? :)
yes .. it has been commited.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Jul 23, 2008 at 19:40, Noah Fontes [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Zülke wrote:
Yeah. We discussed that quite a while back when I sent over the
ignore_errors options patch-like thing in November:
So... who's gonna commit it? :)
David
Am 23.07.2008 um 19:40 schrieb Noah Fontes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Zülke wrote:
Yeah. We discussed that quite a while back when I sent over the
ignore_errors options patch-like thing in November:
David Zülke wrote:
So... who's gonna commit it? :)
I'll commit in the next few hours if nobody objects.
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Jul 22, 2008 at 23:22, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
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.
I think there should be no big
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Zülke wrote:
Yeah. We discussed that quite a while back when I sent over the
ignore_errors options patch-like thing in November:
http://thread.gmane.org/gmane.comp.php.devel/46003
I think we should do it.
But what about other 3xx redirect
-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
Hi!
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.
I think there should be no big problem to allow all 2xx codes, even
though some ones like 204 may behave
14 matches
Mail list logo
