Minor Description
The plugin protocol-okhttp marks content as "truncated" including the reason for the truncation - content limit or time limit exceeded, network disconnect during fetch.
The detection of truncation by content limit has one bug: if the fetched content is exactly the size of the content limit the loop to request more content is exited. It should be continued by requesting one byte more to reliably detect whether content is truncated or not.
Note that the Content-Length header cannot be used to determine truncation reliably: it does not indicate the real content length for compressed or chunked content or it might be wrong.
Attachments
Issue Links
- links to