aws-smithy-http-client 1.4.0

HTTP client abstractions for generated smithy clients
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

# aws-smithy-http-client

HTTP client abstractions for generated smithy clients.

## Connection test harness

The `wire-mock` feature exposes a deterministic connection-level test harness at
`test_util::wire::connection`. Each accepted socket receives one complete script:

```rust,no_run
use aws_smithy_http_client::test_util::wire::connection::{
    ConnectionTestHarness, EndpointPlan, Http1Response, Http1Script,
};
use std::net::{IpAddr, Ipv4Addr};

# async fn example() -> Result<(), Box<dyn std::error::Error>> {
let harness = ConnectionTestHarness::builder()
    .endpoint(
        IpAddr::V4(Ipv4Addr::LOCALHOST),
        EndpointPlan::unbounded(Http1Script::serve(
            Http1Response::ok().body("ok"),
        )),
    )
    .build()
    .await?;

let endpoint = harness.endpoint_url();
// Configure the client with `endpoint` and `harness.dns_resolver()`.

harness.shutdown().await?;
# Ok(())
# }
```

### Multi-address loopback tests

Some tests simulate multiple resolved IP addresses by binding to different loopback addresses
(`127.0.0.1`, `127.0.0.2`, and so on) on the same port. Linux and Windows normally make the full
`127.0.0.0/8` block available without additional setup. On macOS, configure the additional
loopback aliases before running the tests:

```sh
sudo ifconfig lo0 alias 127.0.0.2
sudo ifconfig lo0 alias 127.0.0.3
```

These aliases do not persist across reboots. A test that requires an unavailable loopback address
fails with a message identifying the address and these setup instructions.

<!-- anchor_start:footer -->
This crate is part of the [AWS SDK for Rust](https://awslabs.github.io/aws-sdk-rust/) and the [smithy-rs](https://github.com/smithy-lang/smithy-rs) code generator. In most cases, it should not be used directly.
<!-- anchor_end:footer -->