On Fri, Jun 26, 2026, at 23:41, Jakub Zelenka wrote: > On Fri, Jun 26, 2026 at 5:38 PM Sjoerd Langkemper <[email protected]> > wrote:__ >> On Fri, Jun 26, 2026, at 14:42, Arnaud Le Blanc wrote: >>> Can we deprecate the [dechunk] filter only in php://filter URLs, and not in >>> the function-based filter API? >> Yes. ..., but it won't be a pretty implementation. > Why can't you create a new version of php_stream_filter_create (e.g. > php_stream_filter_create_ex) ...
Ok, that might work. If the implementation won't be a problem we should probably determine what we want from a functional perspective: deprecate dechunk only in php://filter URLs, or for every use? Perhaps we should just put it up to a vote in the RFC? I still think deprecating dechunk completely is a good option. It is not documented. Dechunk decoding is quite easy to implement in user-land PHP, there is no reason it should be provided by PHP itself. Regards, Sjoerd
