On Mon, Jul 27, 2026 at 4:09 PM Matteo Beccati <[email protected]> wrote:
> Hi, > > > On 2026-07-27 12:31, Gina P. Banyard wrote: > >> As announced last week I've opened the vote for the 8.6 mass > >> deprecation RFC: > >> https://wiki.php.net/rfc/deprecations_php_8_6 > At the time I'm the only one who voted "no" on > https://wiki.php.net/rfc/deprecations_php_8_6#deprecate_dechunk_filter > > As things currently stand, projects that rely on this functionality > (notably symfony/http-client and php-http/message) will start triggering > deprecation notices in PHP 8.6. There are no plans to expose the > underlying behaviour in an alternative way, despite this concern being > raised during the discussion period. > > I believe we should provide such an alternative together with the > deprecation, rather than expecting projects with 200M+ installations to > "find an alternative, such as decoding it using code written in PHP". > > I think this should have not been proposed for deprecation yet. There are significant users of it and I just didn't have time to properly look into the issues. So there might be options to get it fixed properly. So I think it should wait till it's properly investigated. Kind regards, Jakub
