HTTP client libraries and wrappers

I read your post on mint and I agree with you. I’m not sure of when they will fix this issue, I urgently need this to be fixed or try another library(any recommendation - processless if possible). Thanks.

As a library user, I expect a library does not touch what I give as much as possible… but as a library author I want to leverage details in specification to make things efficient and simpler.

See Downcase headers when inserting/fetching in HPACK by whatyouhide · Pull Request #172 · elixir-mint/mint · GitHub (I raised this matter there)

This can be a gotcha - e.g. if you build a signature with mixed cases but HTTP library sends a downcased header names… so integration testing is important!

(I was fortunate to get away of bad HTTP server expecting specific case)

I ran into a strange issue today when connecting to an upstream server with Mojito - there’s a custom header which is being converted to lower case, however the upstream server expects the exact casing. Though I think this is a bad design, is there an option to force Mojito or Mint to maintain your case without converting them.

• mojito is a HTTP client based on mint - should have been mentioned!
• tesla 1.3.0 is released, with mint and gun support.
• castore is introduced for mint - See this issue for why new pkg not using certifi.

Oh, ergonomy and convenience. Thanks for clarifying.

No, I mean, the gun use tcp connection and some time we don’t need worries about it and we need just post/get something without knowing of socket or pid of connection. The shot is wrapper of httpc.
Eg: using of gun

{ok, ConnPid} = gun:open("example.org", 443),
StreamRef = gun:get(ConnPid, "/organizations/ninenines").

Eg: using of shot:

shot:get("http://example.org/somedata").

Not sure I understand. You mean you don’t want the HTTP Keep-Alive option used when calling a REST API?

Sure, I know the gun library, but gun use tcp connection, sometime we don’t need to keep connection with some services and just need to call some REST API - what was implemented inside of the shot library

I don’t mean to degrade, just curious if you compared your library to the Gun Erlang HTTP client?

Some time ago I started implement small client library use httpc. This library definitely don’t cover all needs, but I working on it. Recently was added the ability to pass the headers and body of the request as an argument. In any case, this library can be helpful shot - is a small HTTP client library for Erlang.