Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63221
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hoa-project.net from 95.130.12.24 cause and error)
Message-ID: <505C77D9.4010901@hoa-project.net>
Date: Fri, 21 Sep 2012 16:21:13 +0200
Reply-To: ivan.enderlin@hoa-project.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0a2
MIME-Version: 1.0
To: jpauli <jpauli@php.net>
CC: internals@lists.php.net
References: <505C4A06.6040304@hoa-project.net> <CAMUwpuSAjPA+XGXQC38Yiq8f251542vt+vxdw5dw4o0cp3A_eA@mail.gmail.com>
In-Reply-To: <CAMUwpuSAjPA+XGXQC38Yiq8f251542vt+vxdw5dw4o0cp3A_eA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] POST, content-type: application/json and json_decode
From: ivan.enderlin@hoa-project.net ("Ivan Enderlin @ Hoa")


On 21/09/12 16:16, jpauli wrote:
> On Fri, Sep 21, 2012 at 1:05 PM, Ivan Enderlin @ Hoa
> <ivan.enderlin@hoa-project.net> wrote:
>> Hello,
>>
>> If PHP receives a HTTP request with the method POST and with the header
>> Content-Type: application/x-www-form-encoded, then, it automatically parses
>> the request body to populate an array in $_POST. If the Content-Type is
>> different (e.g. text/plain or application/json), the request body is
>> reachable by reading php://input. Well, it is ok.
>>
>> But is there any plans to consider application/json by parsing the request
>> body and populate the result in $_POST (with the help of json_decode()
>> maybe)?
>>
>> If so, I would like to propose a patch but I don't find in the source code
>> where request body is caugth and parsed (for POST). Any ideas?
>> Maybe a RFC would also be welcome to complete my suggestion?
>>
>> Thanks.
> Hi !
>
> Reading and parsing post data function is defined as a SAPI struct
> function pointer.
> You should look at sapi_module_struct definition
> (http://lxr.php.net/xref/PHP_5_4/main/SAPI.h#251).
>
> When a request comes in, sapi_activate() is called. It then calls
> sapi_read_post_data() http://lxr.php.net/xref/PHP_5_4/main/SAPI.c#459
> that itself invokes handlers.
> Default handlers are defined here :
> http://lxr.php.net/xref/PHP_5_4/main/php_content_types.c#29 and for
> POST, by default, sapi_read_standard_form_data() is called (defined
> here http://lxr.php.net/xref/PHP_5_4/main/SAPI.c#253)
> This function is in fact just a bridge, it tells PHP to call
> sapi.read_post() which is a function pointer defined by each SAPI.
> Finally, later on, sapi.default_post_reader() is called (again, a
> function pointer defined by each SAPI)
>
> I agree it's not a very trivial part though :p
No it's clear.
Thanks for clarifying this!

-- 
Ivan Enderlin
Developer of Hoa
http://hoa.42/ or http://hoa-project.net/

PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis)
http://disc.univ-fcomte.fr/ and http://www.inria.fr/

Member of HTML and WebApps Working Group of W3C
http://w3.org/