Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39212
Return-Path: <hannes.magnusson@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 6636 invoked from network); 23 Jul 2008 06:47:44 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 23 Jul 2008 06:47:44 -0000
Authentication-Results: pb1.pair.com smtp.mail=hannes.magnusson@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=hannes.magnusson@gmail.com; sender-id=pass; domainkeys=bad
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.134.189 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: hannes.magnusson@gmail.com
X-Host-Fingerprint: 209.85.134.189 mu-out-0910.google.com  
Received: from [209.85.134.189] ([209.85.134.189:59496] helo=mu-out-0910.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 33/D5-64356-F04D6884 for <internals@lists.php.net>; Wed, 23 Jul 2008 02:47:44 -0400
Received: by mu-out-0910.google.com with SMTP id i2so1478190mue.3
        for <internals@lists.php.net>; Tue, 22 Jul 2008 23:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:cc:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=Wg/9xMpAX51ZAD/+gQ3ZC8Hp1PLi7DRSeJfxyJuXAh0=;
        b=cJufBFcNiEkBNecIPGfuam6s+9G9YCUFZIkKLuKTpgwmzYixVVEM9NleKwa9hCQqe7
         NbXr82UJ2kGnqK40+W/t2sSMwkV0zv1rdJMXkpx8ELkd8RfTBiMI9G4sGOLWTHCQ69q/
         zj52m8Sdv1/WE4Ekfpkjjkn9RqZJbCDHnDy/c=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=hBVQumivur41Za+xIGA4Bh572YHtcJmoQSx5d4I7N5jXU6A5AVtxtTyuWj99mZg2D8
         K1WiR1Eem9eXFp3dGAeT4bGzdEZjZahxQ1jJXQZJS07qMB2O/LRG9dhxks7iLaSkrJ2b
         MDzaLKntcubRgn7116cETBBvSUyP9+iCKkP1E=
Received: by 10.103.200.9 with SMTP id c9mr649563muq.11.1216795660455;
        Tue, 22 Jul 2008 23:47:40 -0700 (PDT)
Received: by 10.103.248.20 with HTTP; Tue, 22 Jul 2008 23:47:40 -0700 (PDT)
Message-ID: <7f3ed2c30807222347k2b1fb52coc24be3f4573af474@mail.gmail.com>
Date: Wed, 23 Jul 2008 08:47:40 +0200
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Noah Fontes" <noah.fontes@bitextender.com>, internals@lists.php.net
In-Reply-To: <48864FA5.6050104@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4885E513.6080702@bitextender.com> <48864FA5.6050104@zend.com>
Subject: Re: [PHP-DEV] Patch for HTTP successful status codes
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

On Tue, Jul 22, 2008 at 23:22, Stanislav Malyshev <stas@zend.com> 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 problem to allow all 2xx codes, even though
> some ones like 204 may behave strangely, but as long as it doesn't break
> anything...

It is a BC break. But people should be checking the retrieved status
codes anyway so I don't think its a big issue.

+1

-Hannes