Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81881
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.174 as permitted sender)
Sender: Michael Wallner <mike.php.net@gmail.com>
Message-ID: <54D330C3.7030001@php.net>
Date: Thu, 05 Feb 2015 09:58:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Stanislav Malyshev <smalyshev@gmail.com>, 
 PHP Internals <internals@lists.php.net>
References: <DDA98D4F-2105-415A-B921-01A622091FA9@php.net> <54D217E7.8030407@php.net> <54D2AE91.8090800@gmail.com> <54D3271E.2080207@php.net> <54D32A38.9050004@gmail.com>
In-Reply-To: <54D32A38.9050004@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] pecl_http
From: mike@php.net (Michael Wallner)

Hi Stas!

On 05/02/15 09:30, Stanislav Malyshev wrote:

>> The sole code change would be removing the check for POST, i.e.
>> `!strcasecmp(SG(request_method),"POST")` so that actually any request
>> method with a recognized content-type (i.e. application/form-data or
>> application/x-www-form-urlencoded) would trigger standard post data
>> handling.
> 
> By "standard post data handling" you mean _POST? I'm not sure it's a
> good idea - it may lead some applications that assume _POST existence
> means POST request into a wrong path, which may have some bad
> consequences as GET and POST to the same URL may have completely
> different meaning in REST application (e.g. GET may be read and POST may
> be write). Why not just let the user ask for data if they need it, but
> keep the environment as is for those that do not need it?

Yes, I mean $_POST (and $_FILES). It's been requested multiple times,
but I know it's quite controversial. I think this approach is better
than any other proposed yet (think $_PUT and stuff).

If I receive form-data or www-form-urlencoded I'd like to have it
readily accessible, but that may only be my opinion, and I definitely
won't insist on it, so if people think this is too much for the naive
application testing $_POST for being a POST, I'll remove it.

Anybody else having an opinon on that matter?


-- 
Regards,
Mike