[php-src] PR #21587: Fix stream filter seeking resetting write filter state on read seeks

From: Date: Tue, 31 Mar 2026 14:43:57 +0000
Subject: [php-src] PR #21587: Fix stream filter seeking resetting write filter state on read seeks
Groups: php.git-pulls 
Request: Send a blank email to git-pulls+get-35450@lists.php.net to get a copy of this message
Pull Request: https://github.com/php/php-src/pull/21587 Author: nicolas-grekas PR #19981 (bug #49874 fix) introduced stream filter seeking, which correctly resets **read** filter state on fseek()/ftell(). However, it also resets **write** filter state on seek, which breaks real-world usage patterns where a stream with a write filter is seeked for reading. The case where this issue happened: php://temp with a dechunk write filter, as used by Symfony HttpClient's NativeResponse to decode chunked HTTP transfers. The buffer is written to (through the filter) and then seeked to position 0 to read back decoded output via stream_get_contents($buffer, -1, 0). After the PR, this seek resets the dechunk filter's state machine to CHUNK_SIZE_START, so the next fwrite() of continuation chunk data is misparsed, causing "Transfer closed with outstanding data remaining from chunked response" errors. The attached patch does this: - **Do not seek/reset write filters on stream seek.** Write filter state tracks the transformation of data being written *through* the filter. It is independent of the stream's read/write position. Seeking repositions where output is stored or read from, not where input comes from. - **Remove the write filter seekability check** that could block fseek(). Since write filters are no longer reset on seek, there is no reason to prevent seeking based on write filter seekability. - Read filter seeking is unchanged and works correctly. This restores the pre-#19981 behavior for write filters (flush-only on seek) while preserving the new read filter seeking behavior. Any code that attaches a stateful write filter (dechunk, zlib.deflate, etc.) to a php://temp or file stream and alternates between writing and reading via stream_get_contents() with an offset is affected by #19981 and fixed here.

« previous php.git-pulls (#35450) next »