http: fix getting Transfer-Encoding value
The 'Content-Length' header was inspected by mistake, which makes it effectively impossible to use chunked Transfer-Encoding when using the http client.
Tested locally with a HTTP server - data is properly sent with POST method and the proper encoding declared, after the fix.
@andrewrk not sure how to ask for review, so I picked&pinged a maintainer, hope it works!
@Vexu (another pseudorandom maintainer pick, I hope you don't mind!), I'm hesitant to rebase to the master branch because the CI takes hours - is it fine if I just leave the PR as is? The change is rather straightforward and shouldn't produce any merge conflicts any time soon