Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76642
Return-Path: <dz@heroku.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 32067 invoked from network); 18 Aug 2014 10:20:43 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Aug 2014 10:20:43 -0000
Authentication-Results: pb1.pair.com header.from=dz@heroku.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=dz@heroku.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.175 as permitted sender)
X-PHP-List-Original-Sender: dz@heroku.com
X-Host-Fingerprint: 74.125.82.175 mail-we0-f175.google.com  
Received: from [74.125.82.175] ([74.125.82.175:60703] helo=mail-we0-f175.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 8E/00-31658-973D1F35 for <internals@lists.php.net>; Mon, 18 Aug 2014 06:20:43 -0400
Received: by mail-we0-f175.google.com with SMTP id t60so4703596wes.6
        for <internals@lists.php.net>; Mon, 18 Aug 2014 03:20:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:content-type:mime-version:subject:from
         :in-reply-to:date:cc:content-transfer-encoding:message-id:references
         :to;
        bh=29pZCPIiFbcXeUWDeOECT20IzBusXF9dzjS81eigICM=;
        b=H7IH4F1qO9ebWGf5csMnx3DwGs9kdIGnLG2HWP74q0gVDOnEI8JYaEzUUH7FXYt2pS
         B+yxOOoikC/oEkn7PpB4G336VOK10I5xkSQXArN747b3yAMNm+vFSnc6oNphtu3YckfS
         Io6k0BMbsQ+1qb903mVG0PrKE7t0G1IDBfusNXm2w38mfFTgJ6gM6CT6tMa46oU6ah9q
         rJQvj8IBzc/41YwvpL7nvWkUDGLKHMG/4k2ytX1yI49zQueeKJ1ca24W5EcYkAftfqK5
         2LSvzQIK1kB33ruxG/qbYluCHfBn/i2oLaGqFBA9rspgVFGlH2VbPjCRr9ezhnrTZAI9
         T2VQ==
X-Gm-Message-State: ALoCoQkiN9IzOPCqHzgs3RrA/yB7SMA2UFdas3qguweSttgd4K9GrR2mxJIxb3qSIQclrALbiWKE
X-Received: by 10.194.76.133 with SMTP id k5mr41617576wjw.28.1408356814788;
        Mon, 18 Aug 2014 03:13:34 -0700 (PDT)
Received: from [192.168.19.33] (178-27-182-9-dynip.superkabel.de. [178.27.182.9])
        by mx.google.com with ESMTPSA id a4sm36396237wie.21.2014.08.18.03.13.33
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 18 Aug 2014 03:13:33 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAGAGxbas-MHC0SVbgNTsYCdr2fQqKaUDax+TiCVDrE-h5wXGXw@mail.gmail.com>
Date: Mon, 18 Aug 2014 12:13:31 +0200
Cc: Thomas Bley <mails@thomasbley.de>,
 "internals@lists.php.net" <internals@lists.php.net>,
 Park Framework <park.framework@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <F3BBB711-6788-4F4C-9F04-061DC010047C@heroku.com>
References: <CAPRqa+G7_quRQ-NR04DChPEZeevuRBHX_1GbOCO+N4VXnzrCTw@mail.gmail.com> <CAGAGxbYjc7MAnKQBNB6hb6StsWaRMshxUZieebmoYXHeNmFGyw@mail.gmail.com> <CAPRqa+Hu4dqCs3X7O+Kh3A15eRQG-savV+2i-R=A3VGp-t6fxA@mail.gmail.com> <20140817021822.9AEBE261C47@dd15934.kasserver.com> <DC15CB30-2B57-4FEF-A679-D82AE02A78F4@heroku.com> <CAGAGxbas-MHC0SVbgNTsYCdr2fQqKaUDax+TiCVDrE-h5wXGXw@mail.gmail.com>
To: Chris Wright <cw@daverandom.com>
X-Mailer: Apple Mail (2.1878.6)
Subject: Re: [PHP-DEV] Native support - PUT request, multipart form data
From: dz@heroku.com (David Zuelke)

On 17 Aug 2014, at 22:55, Chris Wright <cw@daverandom.com> wrote:

> On 17 August 2014 11:49, David Zuelke <dz@heroku.com> wrote:
>> That does not make any sense; applications could accept XML, CSV or =
whatever else just as well.
>>=20
>> The original proposal is not very useful. $_GET contains parsed query =
string info, $_POST contains parsed HTTP request body information if the =
media type is application/x-www-urlencoded or multipart/form-data. =
Deserializing that makes sense as the rules for it are in the HTTP spec.
>=20
> (warning: nitpicking) actually, neither of these types are part of the
> HTTP specification, the protocol specification doesn't deal with how
> to handle content, only how to transmit it. RFC 2616 makes no mention
> of it, and RFCs 7230-7235 don't either.

Sorry, typo, I meant to write HTML.