If the upstream service uses chunked encoding, it will set the Transfer-Encoding header. HTTPoison will decode the chunks and return the entire body but it keeps the header. This results in a violation of the HTTP specification when the response is returned.
Coverage remained the same at 97.297% when pulling 267f736bd7c28df840a8acfca8c95f36b3ae2be4 on tt:drop-transfer-encoding-header into b435e03edd41d10171a18c7cd356a03b7ed9c08a on slogsdon:master.
If the upstream service uses chunked encoding, it will set the
Transfer-Encoding
header. HTTPoison will decode the chunks and return the entire body but it keeps the header. This results in a violation of the HTTP specification when the response is returned.(I apologize that I missed this in #7.)