docs.rs failed to build mio_httpc-0.5.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.
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:
mio_httpc-0.10.5
mio_httpc is an async http client that runs on top of mio only.
For convenience it also provides a SyncCall interface. This is a simple one-line HTTP client operation.
No call will block (except SyncCall), not even for DNS resolution as it is implemented internally to avoid blocking.
It uses http crate for Request/Response types.
mio_httpc requires you specify one of the TLS implementations using features: native, openssl and rtls (rustls). Not picking any feature will NOT work, as all calls will be no-op.
TODO/FEATURE LIST
- Basic API
- Configurable TLS backend
- Chunked encoding download
- Chunked encoding upload
- Basic Auth
- Digest Auth
- Automatic redirects
- Keep-alive connection pool
- DNS retries
- Timeouts
- Websockets
- gzip body decoding
- HTTP2
EXAMPLES
Sync call
extern crate mio_httpc;
use SyncCall;
// One line blocking call.
let = new.timeout_ms.get.expect;
Basic async get
cargo run --example get --features "native" -- "https://edition.cnn.com"
// or
cargo run --example get --features "openssl" -- "https://edition.cnn.com"
// or
cargo run --example get --features "rtls" -- "https://edition.cnn.com"
extern crate mio_httpc;
extern crate mio;
use ;
use ;
Websockets
cargo run --example ws --features="native" -- "wss://demos.kaazing.com/echo"
extern crate mio_httpc;
extern crate mio;
use ;
use ;
// ws://demos.kaazing.com/echo