Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58940
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F610FB9.1060309@lerdorf.com>
References: <4F60F4B1.5010407@lerdorf.com>
	<CAEZPtU6TBV_WrZ_OBY_3EiGO+G5gYQWYDDuKOOfxF3-gO2X-JQ@mail.gmail.com>
	<4F610FB9.1060309@lerdorf.com>
Date: Wed, 14 Mar 2012 23:05:01 +0100
Message-ID: <CAEZPtU7Bfdjherrkp4deAsVShk56HFOmpRoKwK3sqrOaAojFrA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Let parse_str() parse more than max_input_vars args
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Wed, Mar 14, 2012 at 10:38 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> On 03/14/2012 01:32 PM, Pierre Joye wrote:
>> hi Rasmus,
>>
>> As the ini_all option sounds appealing, I can imagine ISPs willing to
>> do not allow their users to change this value, and that's something I
>> would not allow random users either.
>>
>> I'd to go with the optional argument, adding a clear in the
>> documentation about the confusing error message.
>
>  I would think you would have objected to the current INI_PERDIR. This is where a
> user can make his scripts unsafe by disabling max_input_vars in a
> .htaccess file.

I was sure it was system and not per dir.

The ini all option can't hurt more then.

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org