Re: POST, content-type: application/json and json_decode
| From: | Andrew Faulds | Date: | Mon, 24 Sep 2012 18:09:09 +0000 |
| Subject: | Re: POST, content-type: application/json and json_decode | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63231@lists.php.net to get a copy of this message | ||
On 21/09/12 12:05, Ivan Enderlin @ Hoa 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)? I think perhaps that's the wrong approach. It's valid JSON to have a list literal at the top level as well, I think. Perhaps we should introduce a new $_JSON variable or some such thing? $_BODY?
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.-- Andrew Faulds http://ajf.me/