Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78071
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender)
Message-ID: <543D991E.7040405@gmail.com>
Date: Tue, 14 Oct 2014 22:43:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com> <776669CE-9E8C-4069-9834-C7275CCA0EF4@ajf.me> <CAKOpQSwRtSU1LNmftyY1b09SONBCfwS-qiMK4gct6uFiW3CSjw@mail.gmail.com> <CAPhkiZwb13FmX+sQLx0Ki52KuwJ4HWTj-84UqcZq3GYPFL8Tnw@mail.gmail.com> <E8F7D721-767C-4E6E-B0BB-F0DEFEB308B2@ajf.me> <CAF9U7z_0cgwWFEoShU9rJhoOZttztcZk_NAqoXnSuAro-w3kew@mail.gmail.com> <8CB055D4-F164-4DF3-B019-684BAE7E016E@ajf.me> <543D47C1.9050009@lerdorf.com> <etPan.543d4c0e.216231b.12d@Mikes-iMac.local> <543D4CE1.5000109@lerdorf.com> <543D6864.10508@gmail.com> <543D85E6.2020507@lerdorf.com>
In-Reply-To: <543D85E6.2020507@lerdorf.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: rowan.collins@gmail.com (Rowan Collins)

On 14/10/2014 21:21, Rasmus Lerdorf wrote:
> On 10/14/2014 11:16 AM, Rowan Collins wrote:
>> On 14/10/2014 17:18, Rasmus Lerdorf wrote:
>>> I think 20+ years of history has proven this to be a non-issue. Of all
>>> the things that people get confused by in PHP, $_GET/$_POST are right
>>> near the bottom of the list.
>> The popularity of REST is what has changed this. Until people started
>> writing RESTful APIs, only two HTTP request types were in common use.
>> Nobody was confused about where PUT method data would end up, because
>> nobody processed any PUT methods.
>>
>>> It makes no sense to me to make $_BODY an alias for $_POST. $_POST
>>> implies the default body encoding that a broswer performs on a POST
>>> request. Making an alias called $_BODY that doesn't contain the body of
>>> a request unless it is "POST"-encoded would be super confusing.
>> The encoding has no relationship with the request type, even in browsers
>> - the default encoding of a POST form is actually the same encoding used
>> to produce a URL form a GET form.
> Sure, but $_GET/$_POST do. They were not named to match HTTP primitives.
> They were named to match form methods. As in form method="get" and
> method="post". And here the default encoding the browsers use for these
> two methods definitely matter.

Like, I say, application/x-www-form-urlencoded is the default encoding 
for both method="get" and method="post". The difference is that one 
executes an HTTP GET, and appends the encoded data to the request URL, 
while the other executes an HTTP POST, and encloses the encoded data as 
the request body.

Even coming from a browser form, both $_GET and $_POST can be populated 
simultaneously, with independent data:

<form method="post" action="/test.php?foo=query+data"><input 
type="hidden" name="foo" value="body data" /></form>

-- 
Rowan Collins
[IMSoP]