Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51093 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21897 invoked from network); 20 Dec 2010 00:35:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2010 00:35:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.45 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.214.45 mail-bw0-f45.google.com Received: from [209.85.214.45] ([209.85.214.45:34878] helo=mail-bw0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BC/20-18753-0D4AE0D4 for ; Sun, 19 Dec 2010 19:35:29 -0500 Received: by bwz16 with SMTP id 16so3063027bwz.32 for ; Sun, 19 Dec 2010 16:35:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iYBdMhXM2gopVWECFvHv0o1TQJUT7NUyN4hmydQL3oA=; b=Y0jIAo/VNK34K12Y+IdUvvZdSKCUjpptcSdHSaJifzVJDuCzWgXyE77dRRNYMpiiTL JBDczV5eSEui6E+pg1v9TVvlkONcPQ8N7IN52vgyHnCErcqygLPhF7givW/YS6EmPHpM IPoaUIw8HLDvLHxgDhcDM2US7kfYt4jle2x+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KBzN6kFkOYtpEeFgcZcEoCtNNxhB88w9WHb4uDqgTZiYlsrmyriNFFvTuilhogNOeQ qsl4whKjMFEWngBuR3yAdxlbwQzVEdsYzHE54tjGZRo4I1WB+X7nB/jbvoHNkdRjpvvv 2xabJBGhTb/6+oQvG3P0KWTqt01YJkN1tsPU0= MIME-Version: 1.0 Received: by 10.204.98.201 with SMTP id r9mr2976110bkn.37.1292805325230; Sun, 19 Dec 2010 16:35:25 -0800 (PST) Received: by 10.204.52.129 with HTTP; Sun, 19 Dec 2010 16:35:25 -0800 (PST) In-Reply-To: <20101218170656.GA12182@panix.com> References: <20101218170656.GA12182@panix.com> Date: Mon, 20 Dec 2010 01:35:25 +0100 Message-ID: To: Daniel Convissor Cc: PHP Internals List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: pierre.php@gmail.com (Pierre Joye) hi, That was one other thing related to this addition, not specifically the main reason why I think this addition is not as good as expected. Especially as as Gustavo said as well, it is possible to do it using a nice and clean APIs instead of adding yet another cryptic ini setting. I'm not saying that there is no need to improve what this feature does but adding yet another option to deal with HTTP input is somehow very bad. On Sat, Dec 18, 2010 at 6:06 PM, Daniel Convissor wrote: > Hi Pierre: > > On Thu, Dec 16, 2010 at 01:32:15PM +0100, Pierre Joye wrote: > >> However I would >> prefer to bring back a proposal we had a couple of years ago, to >> totally disable post data. > > Completely disabling POST is something that is probably best done > via web server configurations. =A0Doing this at the > applicaiton/programming layer seems like a kludge. > > --Dan > > -- > =A0T H E =A0 A N A L Y S I S =A0 A N D =A0 S O L U T I O N S =A0 C O M P = A N Y > =A0 =A0 =A0 =A0 =A0 =A0data intensive web and database programming > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0http://www.AnalysisAndSolutions.com/ > =A04015 7th Ave #4, Brooklyn NY 11232 =A0v: 718-854-0335 f: 718-854-0409 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org