Re: [RFC] [VOTE] Deprecations for PHP 8.6
| From: | Sjoerd Langkemper | Date: | Wed, 29 Jul 2026 10:02:15 +0000 |
| Subject: | Re: [RFC] [VOTE] Deprecations for PHP 8.6 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-132124@lists.php.net to get a copy of this message | ||
Hi,
Seeing this discussion during the voting phase makes me think the discussion phase wasn't
properly completed yet, and I did a poor job in merging all opinions into a RFC proposal. I would
rather not fuel the discussion any further, but I would prefer to let the voting play out.
Jakub Zelenka wrote:
> The problem is that there wasn't enough time
I don't know your situation, but it seems you have quite a lot of work on your plate. Is there
something I or anyone can do to reduce your load?
> This is exactly a half baked deprecation because ... this does not give us any code removal and
> we still need to maintain it.
This is true, but my goal was to prevent abuse of the dechunk filter in filter chain attacks, not to
reduce maintainance load. See also my PR to make filter chain attacks more difficult: https://github.com/php/php-src/pull/22110
> to properly investigate if the things can be improved on the C side.
I tried some solutions, the most promising here: https://github.com/php/php-src/pull/22548
> There was just some bug and then immediate proposal to deprecate it without first not even
> realising that it's used by chunked encdoing which I needed to point out.
For reference, this was in https://github.com/php/php-src/pull/22036, and
there is some more information in https://github.com/php/php-src/issues/21983.
Regards,
Sjoerd Langkemper