rustmax 0.0.11

A collection of useful crates.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

Low-level HTTP/1 and HTTP/2 implementation for the [`tokio`] ecosystem.

- Crate [`::hyper`].
- [docs.rs](https://docs.rs/hyper)
- [crates.io](https://crates.io/crates/hyper)
- [GitHub](https://github.com/hyperium/hyper)

---

`hyper` is the HTTP implementation underlying [`axum`], [`reqwest`],
and other Rust HTTP libraries.
Most applications should use those higher-level crates;
use `hyper` directly when you need fine-grained control over HTTP connections
or are building your own HTTP framework.

Core types (re-exported from the [`http`] crate):

- [`Request`] / [`Response`] - HTTP request and response, generic over body type
- [`Method`] - HTTP methods (GET, POST, etc.)
- [`StatusCode`] - HTTP status codes (200, 404, etc.)
- [`Uri`] - request URIs
- [`HeaderMap`] - HTTP header collection

## Examples

Working with HTTP request and response types:

```rust
use hyper::{Request, Response, Method, StatusCode};

let req = Request::builder()
    .method(Method::POST)
    .uri("https://example.com/api")
    .header("Content-Type", "application/json")
    .body(())
    .unwrap();

assert_eq!(req.method(), Method::POST);
assert_eq!(req.uri(), "https://example.com/api");

let resp = Response::builder()
    .status(StatusCode::OK)
    .header("Content-Type", "text/plain")
    .body(())
    .unwrap();

assert_eq!(resp.status(), StatusCode::OK);
```

[`tokio`]: crate::tokio
[`axum`]: https://docs.rs/axum
[`reqwest`]: crate::reqwest
[`http`]: crate::http
[`Request`]: crate::hyper::Request
[`Response`]: crate::hyper::Response
[`Method`]: crate::hyper::Method
[`StatusCode`]: crate::hyper::StatusCode
[`Uri`]: crate::hyper::Uri
[`HeaderMap`]: crate::hyper::HeaderMap