Benoit Chesneau
Benoit Chesneau
It's probably because you get the socket from the pool. Bypassing the pool (by setting it to`pool` in the request options would do the trick). If you want to reuse...
I meant settings the pool to none so it's not used :)
@chulkilee you can control connections per pool. Meaning you can start one pool for insecure connections and another cor secured one. Or if you want to use a single connection...
note that if all your connections are closing with the "Connection:close" headers, alls connections are never using the pool (checked in), so it should also work unless there is a...
On Mon 27 May 2019 at 07:02, Chulki Lee wrote: > I did find those workarounds (already mentioned in the body). > > you can control connections per pool. Meaning...
There is a limit of 4096 bytes set to the header line to prevent DoS that may explain the error. It’s not configurable yet. I will add this option. For...
did you try with the latest master?
@prodis bump.
`file` is indeed a specific case if it's your question. It's acting like most server are expecting it. Nothing prevent you to use your own solution either in stream or...
well this is exactly what you can do here: https://github.com/benoitc/hackney/blob/master/src/hackney_multipart.erl#L232 For example: ``` erlang FName = hackney_bstr:to_binary(filename:basename(Path)), MyName = Disposition = {, [{, }, {, }]}, ExtraHeaders = [], {file,...