After a bit of investigation we understand the cause of this issue. It relates to mishandling a response that includes both the Transfer-Encoding and Content-Encoding headers together. If a response includes one or the other by itself the HTTP procedure correctly processes the responses per the RFC you mentioned, this issue only manifests if both headers are included. This will be looked at and addressed in a future release.
... View more
