Be careful with that setting - You may be making yourself vulnerable to DoS
attacks via hash collisions. See
http://isc.sans.edu/diary.html?storyid=12286 and
http://www.phpclasses.org/blog/post/171-PHP-Vulnerability-May-Halt-Millions-of-Servers.html
.

PHP 5.3.9 added a "max_input_vars" setting that essentially does the same
thing as the Suhosin setting. However, the PHP setting only applies at each
level of an array. So, you can have x post variables (including arrays),
and each array can have x values inside it. It sounded like Suhosin has a
global limit, counting every level of the array in the count. Once you're
on PHP 5.3.10, I'd suggest setting PHP's "max_input_vars" setting to
protect yourself against the hash collision DoS attacks.

 - Daniel

On Wed, Feb 8, 2012 at 9:34 AM, Brade <[email protected]> wrote:

> Wow, finally figured it out--it's not a cherokee issue. It's these Suhosin
> PHP settings:
>
> suhosin.post.max_vars
> suhosin.request.max_vars
>
> Apparently each array element in the $_POST data (no matter the depth)
> counts as one variable, so I needed to bump this WAY up from the default
> 200
> (I set mine at 50000 just to be safe).
>
> --
> View this message in context:
> http://cherokee-web-server-general.1049476.n5.nabble.com/Large-POST-forms-not-fully-processed-tp5464749p5464835.html
> Sent from the Cherokee Web Server - General mailing list archive at
> Nabble.com.
> _______________________________________________
> Cherokee mailing list
> [email protected]
> http://lists.octality.com/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to