#named-pipe #windows-named-pipe #hyper #pipe #windows

hyper-named-pipe

Hyper client bindings for Windows Named Pipes

2 releases

0.1.0 Jan 24, 2024
0.1.0-rc1 Jan 20, 2024

#502 in HTTP client

Download history 137240/week @ 2025-12-06 142971/week @ 2025-12-13 77728/week @ 2025-12-20 61569/week @ 2025-12-27 124745/week @ 2026-01-03 311416/week @ 2026-01-10 474130/week @ 2026-01-17 447189/week @ 2026-01-24 410568/week @ 2026-01-31 414358/week @ 2026-02-07 398412/week @ 2026-02-14 460970/week @ 2026-02-21 555200/week @ 2026-02-28 527351/week @ 2026-03-07 401224/week @ 2026-03-14 271871/week @ 2026-03-21

1,838,484 downloads per month
Used in 71 crates (2 directly)

Apache-2.0

11KB
125 lines

crates.io license appveyor docs

Hyper-named-pipe: Hyper client bindings for Windows Named Pipes

Exposes a HTTP interface over Tokio's Named Pipes implementation through a Hyper Connection interface.

Install

Add the following to your Cargo.toml file

[dependencies]
hyper-named-pipe = "*"

Usage

Ensure host's are hex-encoded when passed into HyperUri as this will bypass validation.

let pipe_name = r"\\.\pipe\named-pipe";

let builder = Client::builder(TokioExecutor::new());
let client: Client<NamedPipeConnector, Full<Bytes>> = builder.build(NamedPipeConnector);

let host = hex::encode(pipe_name);
let uri_str = format!("{}://{}", NAMED_PIPE_SCHEME, host);
let url = uri_str.parse().expect("Invalid URI");

async move {
  client.get(url).await.expect("Unable to fetch URL with Hyper client");
};

Tests

It's possible to run the unit test on a unix platform using the cross helper:

cross test --target i686-pc-windows-gnu

Dependencies

~4–7.5MB
~127K SLoC