nightfly 0.1.3

higher level HTTP client library for the lunatic runtime
docs.rs failed to build nightfly-0.1.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: nightfly-0.1.6

nightfly

This project is an ongoing effort to port the reqwest library to the lunatic runtime

What works:

  • json, text and bytes for request and response bodies
  • decompression with brotli, gzip and deflate
  • redirect handling
  • cookies
  • chunked responses
  • handling of multiple open tcp streams per client
  • timeouts (not sure how this should look like in a lunatic setup)
  • Piping of responses (requires chunk-encoding)
  • pooling of connections (needs more usage of lib to find a good approach)
  • proxy handling
  • upgrade, socks5 support and websockets
  • custom dns resolver

MIT/Apache-2 licensed CI

An ergonomic, batteries-included HTTP Client for the lunatic runtime written in Rust.

  • Plain bodies, JSON, urlencoded, multipart (see examples)
  • Customizable redirect policy (IN PROGRESS)
  • HTTP Proxies (IN PROGRESS)
  • HTTPS via lunatic-native TLS (see examples)
  • Cookie Store (IN PROGRESS)
  • Changelog

Example

This example uses Lunatic and enables some optional features, so your Cargo.toml could look like this:

[dependencies]
nightfly = { "0.1.0" }
lunatic = { "0.12.0" }

And then the code:

use std::collections::HashMap;

#[lunatic::main]
fn main() {
    let resp = nightfly::get("https://httpbin.org/ip")
        .unwrap()
        .json::<HashMap<String, String>>()
        .unwrap();
    println!("{:#?}", resp);
    Ok(())
}

Requirements

License

Licensed under either of

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.