Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50904 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20319 invoked from network); 7 Dec 2010 18:18:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2010 18:18:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.170 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:40591] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 31/77-04382-E7A7EFC4 for ; Tue, 07 Dec 2010 13:18:39 -0500 Received: by gyf2 with SMTP id 2so172889gyf.29 for ; Tue, 07 Dec 2010 10:18:35 -0800 (PST) Received: by 10.151.7.18 with SMTP id k18mr2253669ybi.348.1291745915647; Tue, 07 Dec 2010 10:18:35 -0800 (PST) Received: from Anonymous.local ([66.201.49.171]) by mx.google.com with ESMTPS id 3sm1612039yhl.0.2010.12.07.10.18.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 07 Dec 2010 10:18:33 -0800 (PST) Message-ID: <4CFE7A76.9020008@lerdorf.com> Date: Tue, 07 Dec 2010 10:18:30 -0800 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Gustavo Lopes CC: "internals@lists.php.net" References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: rasmus@lerdorf.com (Rasmus Lerdorf) On 12/6/10 11:08 PM, Gustavo Lopes wrote: > 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. I'm ok with it. It's a bit awkward having disable=on to disable something though. Generally we prefer enable=off because it causes fewer brain injuries. -Rasmus