Re: Native support - PUT request, multipart form data
| From: | David Zuelke | Date: | Mon, 18 Aug 2014 10:13:31 +0000 |
| Subject: | Re: Native support - PUT request, multipart form data | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-76642@lists.php.net to get a copy of this message | ||
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.
>>
>> 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.
>
> (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.