Crates.io | proto-tower-http-2 |
lib.rs | proto-tower-http-2 |
version | |
source | src |
created_at | 2025-01-28 22:15:58.508715+00 |
updated_at | 2025-02-18 16:23:41.487692+00 |
description | Tower implementation of the HTTP/2 protocol |
homepage | |
repository | |
max_upload_size | |
id | 1534089 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
H2 is the HTTP/2 protocol over TLS. This is the most common way to use HTTP/2.
H2C is the HTTP/2 protocol without the TLS layer. This is useful for when you want to use HTTP/2 but don't want to deal with the complexity of TLS.
The TLS layer can be injected separately. This crate handles the HTTP/2 protocol with or without TLS.
https://www.rfc-editor.org/rfc/rfc7540
[dependencies]
proto-http-2 = { git = "https://github.com/rapidrecast/proto-tower.git", subdir = "proto-http-2" }
If you are upgrading to http 2 from http 1, you should NOT do that if the upgrade protocol is h2c.
From the RFC: