Re: max_input_vars silently truncates input without an error message

From: Date: Thu, 20 Nov 2025 18:59:43 +0000
Subject: Re: max_input_vars silently truncates input without an error message
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-129345@lists.php.net to get a copy of this message 
On Thu, Nov 20, 2025 at 2:00 PM Andrey Andreev <narf@devilix.net> wrote:
>
> Hi Brady,
>
> I agree that E_WARNING is a poor way to handle this limit, and IMO a fatal error should be
> triggered instead. The ability to suppress and ignore is the root cause of why your situation is
> possible at all, and Laravel's behavior in this instance also did you a massive disservice.
>
> That being said however, this is also an extreme and self-inflicted edge case. 1k is an absurd
> number, even 100 input vars should be a sign of poor code logic. I urge you to redesign your
> solution entirely instead of looking for a quick workaround.

In our case, we had a multi-select (<select> with the 'multiple'
attribute) that listed a few thousand users. You can select them all,
and each selected value counts towards the 1000 fields being
submitted. You could argue that it's poor design, and, maybe, it could
be. But it's still a valid use-case IMHO.

-B.

Thread (7 messages)

« previous php.internals (#129345) next »