Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50889 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45863 invoked from network); 7 Dec 2010 10:27:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2010 10:27:52 -0000 X-Host-Fingerprint: 78.142.172.145 gate-g21.inqnet.at Received: from [78.142.172.145] ([78.142.172.145:4477] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D5/70-40992-62C0EFC4 for ; Tue, 07 Dec 2010 05:27:51 -0500 Message-ID: To: internals@lists.php.net Date: Tue, 07 Dec 2010 11:27:48 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101028 Lanikai/3.1.6 MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 78.142.172.145 Subject: Re: [PATCH] Add option to disable POST data processing From: mike@php.net (Michael Wallner) On 12/07/2010 08:08 AM, Gustavo Lopes 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. > > 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? > Definitely +1.