Provides utilities to host a [axum-server] server that
accepts the HTTP and HTTPS protocol on the same port. See
[bind_dual_protocol()].
A common use case for this is if a HTTPS server is hosted on a
non-traditional port, having no corresponding HTTP port. This can be an
issue for clients who try to connect over HTTP and get a connection reset
error. See [ServerExt::set_upgrade()].
The simplest way to start is to use [bind_dual_protocol()]:
```rust
let app = Router::new().route("/", routing::get(|| async { "Hello, world!" }));
// User-supplied certificate and private key. let config = RustlsConfig::fromder(certificate, privatekey).await?;
axumserverdualprotocol::binddualprotocol(address, config) .serve(app.intomake_service()) .await?; ```
We now have a server accepting both HTTP and HTTPS requests! Now we can
automatically upgrade incoming HTTP requests to HTTPS using
[ServerExt::set_upgrade()] like this:
```rust
use axumserverdual_protocol::ServerExt;
axumserverdualprotocol::binddualprotocol(address, config) .setupgrade(true) .serve(app.intomakeservice()) .await?; ```
Alternatively [UpgradeHttpLayer] can be used:
rust
let app = Router::new()
.route("/", routing::get(|| async { "Hello, world!" }))
.layer(UpgradeHttpLayer);
As this library heavily relies on [axum-server], [axum],
[tower] and [hyper] the MSRV depends on theirs. At the point of time
this was written the highest MSRV was [axum] with 1.60.
See the [CHANGELOG] file for details.
Licensed under either of
at your option.
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.