This happens when the result has the Content-Length header instead of using chunked encoding.
Fixed in release 1.1.5.
Log in to post a comment.
Fixed in release 1.1.5.