Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50888
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 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=lWHj6mFnnoDK/yz7scYkJ2rnWBElzkLhX9AqyQmkPQz2OJZ4x9/NlfCTuyZxLRAmYO
         txO7IGxVCo89jYAFl20du9xaN81yRHMJJ2meTobw01H+1A2F1mZ9PGUHWeENulkDjHOq
         ne8sC/Nq55s0axF0t/M9FEMBf9V7srXS4Apy4=
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: Tue, 7 Dec 2010 09:25:26 +0100
Message-ID: <AANLkTik7Poia2XXsqvUZV9hHXFDbC=h1-QB9kA=tyZrR@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=00163631084323b1010496cdbf90
Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing
From: info@tyrael.hu (Ferenc Kovacs)

--00163631084323b1010496cdbf90
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?
>
>
I like the idea.

Tyrael

--00163631084323b1010496cdbf90--