v5.9.1
Highlights
- Fixed #236: downloaded file truncated when a caller's custom HttpClient auto-decompresses gzip/deflate content. The server advertises a Content-Length equal to the compressed byte count, so chunking against that number and writing the decompressed bytes overran and cut the file short. The size probe (SocketClient) now treats a non-identity
Content-Encodingon the response as unknown size + no range support, routing such downloads through the existing single-connection / unknown-size path instead of splitting the compressed length into parallel range chunks. - Guidance: a transparently-compressed URL is downloaded on a single connection because a gzip stream cannot be range-split by output-byte offset. To keep multi-part parallel download for such a URL, set
AutomaticDecompression = Noneon your custom HttpClient so the bytes on the wire match the advertised Content-Length and the file stays range-addressable.
Full Changelog: v5.9.0...v5.9.1