An issue exists where `HTTPResponse.stream` and `HTTPResponse.read chunked` can enter an infinite loop. This occurs when a server sends a chunked Deflate response (Transfer-Encoding: chunked and Content-Encoding: deflate) where the decoded body exceeds a positive finite chunk size and the encoded body contains trailing bytes. The Deflate decoder retains these trailing bytes as unconsumed input after reaching the end-of-stream and repeatedly decodes them without progress. This leads to excessive CPU usage and prevents the request from completing, as network read timeouts do not interrupt the loop since no further socket reads occur.