Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58952 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48202 invoked from network); 15 Mar 2012 06:41:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2012 06:41:57 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.163 smtp163.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.163] ([207.97.245.163:47234] helo=smtp163.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 85/51-40094-43F816F4 for ; Thu, 15 Mar 2012 01:41:56 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp46.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id A5CCEE846C; Thu, 15 Mar 2012 02:41:53 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp46.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 43A67E8320; Thu, 15 Mar 2012 02:41:53 -0400 (EDT) Message-ID: <4F618F30.7060209@sugarcrm.com> Date: Wed, 14 Mar 2012 23:41:52 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: Ryan McCue CC: "internals@lists.php.net" References: <4F60F4B1.5010407@lerdorf.com> <4F611045.8040404@rotorised.com> In-Reply-To: <4F611045.8040404@rotorised.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Let parse_str() parse more than max_input_vars args From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > That's probably going to confuse people if it doesn't change the HTTP > request parsing limit too, IMHO. And I'm not sure that's something we > necessarily want. Err, how you can change it after HTTP request has already been parsed? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227