Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51993
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=TT4Wo+rPVDbrnyQ5c2SoyTq9gjs7VMpTQtemew6s9ZLkj0O4QbDfkdexEzuoWoJyRM
         StjWfFn7Lg/uk0t7OobsLK0OnecKt3BVwYea7PoWEqabnt3+G8SunKWByAOf9UuRd9gk
         EUlPZ2n/iKoWMxiAr3dX+AfQvYyAZmkWcL4nI=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <op.vnb0shjiidpuyk@damnation.dulce.lo.geleia.net>
References: <op.vnb0shjiidpuyk@damnation.dulce.lo.geleia.net>
Date: Sat, 23 Apr 2011 15:23:00 +0200
Message-ID: <BANLkTinf8u33FHnj8VpjSH=hh1Em99cxUw@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=0016364c71afa1aba704a195dfe6
Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing
From: info@tyrael.hu (Ferenc Kovacs)

--0016364c71afa1aba704a195dfe6
Content-Type: text/plain; charset=UTF-8

On Tue, Dec 7, 2010 at 8:08 AM, Gustavo Lopes <glopes@nebm.ist.utl.pt>wrote:

> The very simple attached patch adds an option to disable POST data
> processing, which implies the data can only be read in a stream fashion
> through php://input.
>
> As far as I know, PHP offers no way to inhibit processing RFC 1867 data and
> one has to use very hacky means to accomplish that. This is often required
> (or at least convenient) in order to, e.g., proxy requests or handle file
> uploads in memory.
>
> For other types of requests, the default processing of POST data may also
> be a problem. Take a non-application/x-www-form-urlencoded POST requests
> (say, some kind of RPC with a big XML payload) -- PHP is very memory
> inefficient as it will hold the whole POST data into memory and duplicate it
> twice (from SG(request_info).post_data to $HTTP_RAW_POST_DATA -- even if
> always_populate_raw_post_data=0 -- and SG(request_info).raw_post_data).
>
> This introduces a new ini setting, disable_post_data_processing, but it's a
> benign one. No incompatibilities between setups will arise because no one
> will enable it globally (it would be insane), only selectively to the
> scripts that require it. The reason for an ini setting is that it must be
> set early in the request life.
>
> Thoughts?
>
> --
> Gustavo Lopes
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Did we agree on something about this improvement/patch?
as I said, I like the idea, but if we cannot agree on the details(how to
control that which script needs this), could we somehow at least make it
possible to read the raw post through php://input for "multipart/form-data"
requests?
currently just no way to read the raw data for those requests which sucks
big time.

Tyrael

--0016364c71afa1aba704a195dfe6--