Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51063 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29811 invoked from network); 16 Dec 2010 21:34:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2010 21:34:02 -0000 Authentication-Results: pb1.pair.com header.from=keisial@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=keisial@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: keisial@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-ww0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:36492] helo=mail-ww0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 42/00-29115-8C58A0D4 for ; Thu, 16 Dec 2010 16:34:01 -0500 Received: by wwb31 with SMTP id 31so2610wwb.11 for ; Thu, 16 Dec 2010 13:33:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=jHHn0LXqs8jagR69UIaaOc0k+4ObxCccPA2+MV6Lsag=; b=YfFkpLK/pzq/kzutCaRmq9Gl42ryRDWxp+DjRO/Crr5l5KNjCVJT7XEytJ5RU2ysPn kjN50KJUZ7rJwxNvSb2BJHbKHUZJqOvuXqXvvZQjKGOyfQg+vXEC/AOqORYT1fb3vaIv pKvz/K5JGOCDAft0fbLiCTxMeviO5Odg8vJL0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=RX52Ay73jYIG8yfVttlSJ1UP6euAqHbf7HW7WdaXqYNGqsw4KF4vVAZQZixn4VmpTX kpB/Mu6x3orM7mGX9tsLkqVxZmqlOElLGi9m/EGBBsE2cdKbABJvc8qyklh/te4Kd42S e+vuezTXGUIp2O0tdjy393xIE51X/7zma7PVg= Received: by 10.216.208.230 with SMTP id q80mr2783621weo.103.1292535237334; Thu, 16 Dec 2010 13:33:57 -0800 (PST) Received: from [192.168.1.26] (106.Red-83-44-158.dynamicIP.rima-tde.net [83.44.158.106]) by mx.google.com with ESMTPS id o19sm298473wee.2.2010.12.16.13.33.54 (version=SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 13:33:56 -0800 (PST) Message-ID: <4D0A8632.4060501@gmail.com> Date: Thu, 16 Dec 2010 22:35:46 +0100 User-Agent: Thunderbird MIME-Version: 1.0 To: Gustavo Lopes , PHP Developers Mailing List References: <6b2ba5e56d64910c49bb431ba1e36e17@nebm.ist.utl.pt> <59.E3.36789.3D72A0D4@pb1.pair.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: keisial@gmail.com ("=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=") Gustavo Lopes wrote: > I know you're responding to Pierre's proposed addition of a way to > disable POST data handling altogether possibly via an ini option, but > since the objection also applies to the ini option I've added to > trunk, I'd like to address it. > > Yes, it sucks that the option cannot be changed with ini_set, but > that's an inevitable technical limitation that I don't see how it can > be overcome without major changes. By the time control is passed to > the script, the interesting stuff has already happened. > > (By the way, I think it's unfortunate that most frameworks abandoned > the simplicity of a direct correspondence file <--> url -- whenever > practical, of course, but that's another matter) It could be a set-only option. You can't disable it, but if it isn't set and you enable it, it magically fills your $_POST. Making the internal function available to the userland would be preferable, though. That would be more flexible even though the common usecase would be $_POST = process_post("php://input");