Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50896 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67407 invoked from network); 7 Dec 2010 12:37:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2010 12:37:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.54 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.83.54 mail-gw0-f54.google.com Received: from [74.125.83.54] ([74.125.83.54:46918] helo=mail-gw0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/F3-40992-19A2EFC4 for ; Tue, 07 Dec 2010 07:37:38 -0500 Received: by gwj21 with SMTP id 21so7282425gwj.13 for ; Tue, 07 Dec 2010 04:37:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=htOSCO0lDxj4/R3Rf0pP1GeroYfwuyFnBN3dBkSP12k=; b=l/Ycb2S19dd1Q1ikQETfJ8BdbHleqpbZXsp9O1QWcflRglqnDgav1JUe7WSdXZ7Y/L pN6Kg8w/FJKyad0ZTERqZkXkktZWor5LxKGwBj5WmtYIlHlG/ICNI44n/yO2qfGK3iIK pYHW2+jOKJV9jz+99w8ex5w88L1jrjKEoU3eI= 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=xaXrUOkhZkp+2Dx6i5Lg/stWqPG1yktjK7MBXPU/gyzkkuRM7zyzqj8WnC/CKyjFU1 jyHFpqHyIQz82la0LlnKgDVc4oqNUbh/+C1EeMF1dn+3Nyg/CDT+L2C0Axnx4WuHwHDe nTGrCRvg2eEeJnoC+TZ5jBGe0C08nbse8TcMI= MIME-Version: 1.0 Received: by 10.90.3.31 with SMTP id 31mr9555953agc.141.1291725455201; Tue, 07 Dec 2010 04:37:35 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.90.53.4 with HTTP; Tue, 7 Dec 2010 04:37:35 -0800 (PST) In-Reply-To: References: Date: Tue, 7 Dec 2010 13:37:35 +0100 X-Google-Sender-Auth: yRlAgNFl3I1AbtyhGTYvCBBsYS4 Message-ID: To: Derick Rethans Cc: Gustavo Lopes , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001636310843e794e30496d1446f Subject: Re: [PHP-DEV] [PATCH] Add option to disable POST data processing From: info@tyrael.hu (Ferenc Kovacs) --001636310843e794e30496d1446f Content-Type: text/plain; charset=UTF-8 On Tue, Dec 7, 2010 at 1:01 PM, Derick Rethans wrote: > On Tue, 7 Dec 2010, 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. > > Does without this patch, reading POST data from php://input work? > yep. you will get the raw post data with this. same as $HTTP_RAW_POST_DATA the only difference, that the latter isn't always available. > > > 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), > > Because they can, people will do it though... I'm not fan of more ini > settings. > so because in the past ini settings was abused,we won't add ini settings ever? Tyrael --001636310843e794e30496d1446f--