Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77977
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain benramsey.com from 209.85.216.175 cause and error)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>
Date: Tue, 14 Oct 2014 08:09:41 -0500
Cc: PHP internals list <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <9CAD580B-48C1-4D91-B761-20F8A9804A66@benramsey.com>
References: <CAKOpQSwS=Xck41sQQyEYGG8L3VHq+fRWjy0dDorbwZaVWMLCow@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: ben@benramsey.com (Ben Ramsey)

On Oct 14, 2014, at 7:47 AM, Kris Craig <kris.craig@gmail.com> wrote:

> Hey guys,
>=20
> Does anybody know why we have $_GET and $_POST, but not $_PUT and
> $_DELETE?  As far as I can tell, the only way to get these out =
currently is
> to parse their values by reading the incoming stream directly.
>=20
> Is there a reason why we don't want this or is it just that nobody has
> actually written it yet?
>=20
> =97Kris

This is due to the history of HTML forms sending POST requests with the =
Content-Type application/x-www-form-urlencoded. That is, all the fields =
are key/value pairs and may be easily converted into a PHP array. If you =
use POST with application/json, nothing appears in $_POST, for example.

In practice, we could support $_PUT and $_DELETE for requests that use =
application/x-www-form-urlencoded, but most folks implementing PUT and =
DELETE do not use application/x-www-form-urlencoded for these requests.

I would venture to say that most people implementing PUT requests accept =
application/json and most DELETE requests have no body at all. So, $_PUT =
and $_DELETE superglobals wouldn=92t make sense.

-Ben