hackney
hackney copied to clipboard
benoitc
simple HTTP client in Erlang
I ran into an issue where a remote server would refuse data (inside a multipart) unless the `Content-Disposition` header contained a filename, but I couldn't find any way to set...
There seems to be some sites that return status codes as floats e.g. `http://www.lowiqcanadian.com/id2.html`. When running `curl --head http://www.lowiqcanadian.com/id2.html` we see that the status code returned is actually a `401.1`...
Hi Benoît, The destination ip address selection in hackney may be problematic in some dual stack environment. Since behavior in these environment is not configurable in hackney and sometimes incompatible...
Noticed that if the proxy transport is https and the end transport is https -> the request will return invalid_proxy_transport. This seems like https proxies are not supported or am...
Trying to bump `parse_trans` to the latest version. I am not very familiar with erlang/rebar, please bear with me.
So, should add `Accept-Encoding: gzip,deflate` to request, then check for `Content-Encoding: gzip` or `Content-Encoding: deflate` and decompress body (after de-chunking). Decompression may be done in single pass (`zlib:gunzip/1` for gzip...
Remove the bad protocol from the URL instead of parsing that protocol inside the domain.
```Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.```...
Fixes #635 I'm not sure if I need to make other changes. Did a few searches on the codebase and did not find obvious things to change. Let me know...
When `hackney` consumes a chunked response, it always waits until an entire chunk is available before sending it to a client process even when used asynchronously. I do understand why...
