Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118616
MIME-Version: 1.0
References: <8479bc9a-6ed6-0cf1-c727-123e2b87a8d6@dafert.at>
In-Reply-To: <8479bc9a-6ed6-0cf1-c727-123e2b87a8d6@dafert.at>
Date: Tue, 13 Sep 2022 11:29:41 -0700
Message-ID: <CAMrTa2GQKqGZmijcOmSeTSak3385H6eiSUe0PTQXcCMHwpKQww@mail.gmail.com>
To: Mel Dafert <mel@dafert.at>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000c0040f05e893325b"
Subject: Re: [PHP-DEV] Error behaviour for max_input_vars
From: jordan.ledoux@gmail.com (Jordan LeDoux)

--000000000000c0040f05e893325b
Content-Type: text/plain; charset="UTF-8"

On Tue, Sep 13, 2022 at 10:59 AM Mel Dafert <mel@dafert.at> wrote:

>
>      (This happens in the legacy application I am working on, I do not
> see it changing anytime soon.)
>
>
All of these solutions would be available in some future version of PHP.
While your situation highlights something that might be broadly applicable
to PHP, you'd likely have to update the legacy application to take
advantage of any solution that was eventually included so that it could run
on the most recent version of PHP. Unless you're suggesting that this would
also be backported? 7.4 falls out of all support in a few months.

Just want to make sure you're aware of how the inclusion process would work
for any solution to this issue.

Jordan

--000000000000c0040f05e893325b--