ureq VS curl-rust

I also enjoyed using ureq as an http client.

After a quick check of the available rust http client libraries I opted for reqwest. It has a pretty simple API and it seems to be among the most used libraries for this matters. But I'm a bit concerned about all its dependencies so I might try ureq later.

Async is only useful when you have hundreds of connections open at the same time and idling most of the time; otherwise it's a liability. If your web API does not allow that (e.g. it has rate-limiting, which most APIs do), I suggest going with a client that performs blocking I/O and spawning threads if you need parallelism. https://github.com/algesten/ureq should fit the bill.

I think you'll find a lot of people claiming its overkill, but it will have excellent documentation for both sides, offer reasonable speed, and let you hash out the actual logic of your system without worrying too much about if your low-level implementation is correct. Two good frameworks for the server would be Actix or Rocket. For the client, i'd reccomend either using reqwest or ureq. From there, you can just set up a few POST endpoints, and get to going.

If you want an HTTP client with few dependencies and little unsafe code, take a look at https://github.com/algesten/ureq

Give ureq a try: https://github.com/algesten/ureq

Under the hood, Hurl uses curl with Rust bindings (thanks to the awesome curl-rust crate)

Hurl can't exist without a lot of crates, and particularly curl-rust https://crates.io/crates/curl. Huge thanks to the maintainers!

Looking at commit history, cargo feature adding ntlm support has been added after latest release and is currently only on git.

I was working on a similar thing. Instead of hyper, curl-rust was sufficient. You get features from libcurl like TTFB