Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78098
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ralphschindler.com from 209.85.218.47 cause and error)
Message-ID: <543EE3B8.7010407@ralphschindler.com>
Date: Wed, 15 Oct 2014 16:14:32 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; 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>	<CAKOpQSyTSZeXppZ-f9OeNfA9=Q58jte1fH6zcuzxYZ+qK7-6JA@mail.gmail.com>	<57b7a3681d6c2c7ae123c8921b2d19d6@mail.gmail.com>	<CAPRqa+HZz2UKS564QAeyvLLUByNYLPZ7UCL7oYcgxHxn2R+8Yg@mail.gmail.com>	<543DCE2B.8010506@sugarcrm.com> <CAPRqa+Ey4AEFGhxedOOC2A5AR==jgkZHHmQ9rjY5fxOW1og_yw@mail.gmail.com>
In-Reply-To: <CAPRqa+Ey4AEFGhxedOOC2A5AR==jgkZHHmQ9rjY5fxOW1og_yw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] New globals for PUT and DELETE
From: ralph@ralphschindler.com (Ralph Schindler)

>> I'm not sure I understand what you're trying to do, could you explain in
>> more detail with examples?
>
> PUT /url
> Content-type: application/x-www-form-urlencoded
>
> parse_str (file_get_contents(‘php://input'), $_POST) // Ok
>
> PUT /url
> Content-type: multipart/mixed; boundary="xxxx"
>
> file_get_contents(‘php://input') // Empty string

You are missing information in your example.  First, PHP doesn't do 
content negotiation for every Content-Type known to send serialized 
data, it is extremely selective in that AFAIK, url/form encoded 
Content-Types, when POSTed, will be content-negotiated, parsed, and 
their resultant will populate the $_POST superglobal.

Moreover, your 2nd example does not suggest that an HTTP request was 
sent with a body to demonstrate there is a bug here.

With a php script being served at index.php with the following contents:

   <?php
   var_dump(file_get_contents('php://input'));

Here is a demonstration of this script, and a successful read of the 
request body:

   $ echo 'FOOOO=BARRRRR' | http --verbose PUT localhost:8000 \
     Content-Type:'multipart/mime; boundry=xxxxx'

   PUT / HTTP/1.1
   Accept: application/json
   Accept-Encoding: gzip, deflate
   Content-Length: 14
   Content-Type: multipart/mime; boundry=xxxxx
   Host: localhost:8000
   User-Agent: HTTPie/0.8.0

   FOOOO=BARRRRR

   HTTP/1.1 200 OK
   Connection: close
   Content-type: text/html
   Host: localhost:8000
   X-Powered-By: PHP/5.5.15

   string(14) "FOOOO=BARRRRR
   "


-ralph