h3-forked
An independently published fork of hyperium/h3. It publishes upstream HTTP/3 and WebTransport changes, including independently validated contributions awaiting upstream review, without requiring consumers to use Git dependencies, Cargo patches, or a private registry.
This is not an official Hyperium release. The implementation remains experimental; publishing this fork does not imply API stability or production readiness.
Packages
All four packages live in this repository and depend on the forked family:
| Package | Version | Rust crate name |
|---|---|---|
h3-forked |
0.0.4 |
h3 |
h3-quinn-forked |
0.0.4 |
h3_quinn |
h3-datagram-forked |
0.0.4 |
h3_datagram |
h3-webtransport-forked |
0.0.4 |
h3_webtransport |
The four packages share one release version, starting at 0.0.1. Every family
release advances all four packages together, independently of upstream version
numbers. The 0.0.x fork line starts at 0.0.1 on the upstream 0.0.8
baseline. If upstream 0.0.9 is adopted as the next baseline, the fork family
starts a 0.1.x line at 0.1.0. Merged changes within the current baseline
advance the current fork line when published.
The shared version is defined in the root Cargo.toml under
[workspace.package]; intra-family version requirements are updated with it.
The initial fork is based on
upstream commit 43745ad,
including all changes merged through that commit.
Release 0.0.4
The upstream baseline remains 43745ad87e95b0c035ac9c547aad467303213425:
H3 0.0.8, Quinn adapter 0.0.10, Datagram 0.0.2, and WebTransport 0.1.2.
The official Quinn 0.11 dependency is unchanged.
This release incorporates the following upstream contributions as its implementation baseline. They are still under review, not merged upstream:
- #381: separate the connection driver from individual WebTransport sessions.
- #382: observe CONNECT closure independently of the driver.
- #383: send and receive session close capsules, retaining the application code and reason and terminating only that session's streams.
- #384: map data stream application errors to and from the WebTransport HTTP/3 error range.
The exact contribution commits are retained in the fork's ancestry through
7ed042e.
The first two changes already shipped in fork 0.0.2 and 0.0.3, respectively.
The last two ship in 0.0.4; all four fork packages advance together. The Quinn
adapter also makes pending reads cancellation-safe so session termination can
stop an outstanding receive.
For migration from 0.0.3, session.closed() now returns SessionClose with
the code and reason. Session termination resets its data streams; callers still
own graceful drain before closure. Inherent stream reset and stop_sending
methods accept u32 application codes; the h3::quic traits retain raw wire
codes. See the WebTransport API notes.
Release 0.0.3
The upstream baseline remains 43745ad87e95b0c035ac9c547aad467303213425:
H3 0.0.8, Quinn adapter 0.0.10, Datagram 0.0.2, and WebTransport 0.1.2.
The official Quinn 0.11 dependency is unchanged.
WebTransport adds session.closed().await to observe CONNECT FIN, reset or
connection loss without taking the connection driver or terminating admitted
streams. Waiting is cancel-safe and retains its result for concurrent and
subsequent callers. It does not interpret capsule close codes; GOAWAY alone
does not complete it. Stream admission and graceful drain remain caller-owned.
All four fork packages advance together to 0.0.3. There are no further API
migrations beyond selecting this family version consistently; the connection
and session ownership model introduced in 0.0.2 remains unchanged.
Release 0.0.2
The upstream baseline remains commit
43745ad:
H3 0.0.8, Quinn adapter 0.0.10, Datagram 0.0.2, and WebTransport 0.1.2.
The official Quinn 0.11 dependency is unchanged.
This release separates the WebTransport connection driver from individual
sessions. It is a breaking API change from fork 0.0.1: consumers must keep
driving incoming HTTP/WT streams and route them by session ID rather than
handing the connection to a session. See the
WebTransport migration notes.
All four fork packages advance together to 0.0.2; upstream package versions
have not changed.
Dependencies
Use the crates.io packages with aliases to retain the upstream Rust import names:
[]
= { = "h3-forked", = "0.0.4" }
= { = "h3-quinn-forked", = "0.0.4", = ["datagram"] }
= { = "h3-webtransport-forked", = "0.0.4" }
For direct HTTP Datagram access, add:
= { = "h3-datagram-forked", = "0.0.4" }
h3-quinn-forked uses the official Quinn 0.11 series and accepts its
quinn::Connection directly. Add quinn with the runtime and TLS features your
application needs. A separate Quinn fork or Hyper integration is not required.
Use this fork family consistently wherever H3 types cross crate boundaries;
aliasing h3-forked does not change another dependency's upstream h3 types.
Using quinn-deferred-config
For virtual hosting on a shared QUIC endpoint, this family can be used with
quinn-deferred-config.
During the QUIC handshake, the application uses the ClientHello's SNI to select
the virtual host's rustls::ServerConfig, including its certificate and TLS
policy, within the official Quinn stack. The resulting quinn::Connection is
used directly by h3-quinn-forked for HTTP/3 and WebTransport.
We maintain both projects. Updates to this fork and quinn-deferred-config
will be coordinated to keep their supported Quinn and Rustls versions
compatible, so applications can continue to use them together. Applications
choose whether to use deferred configuration; it is not a dependency of the
H3 fork family.
Upstream and maintenance
See the upstream README for the project
overview, design, and protocol documentation. The local examples
use this fork's packages. Upstream adapters that depend on the original h3
package need to be adapted before they can be used with this fork.
master tracks upstream. forked/0.0.8 receives upstream history and validated
contribution branches by merge. The branch name records the original upstream
version; fork releases use their own shared version. Unmerged contributions
are identified above and reviewed again when upstream accepts or revises them.
Keep general protocol changes on upstream contribution branches, with their commits preserved in the fork's ancestry. Fork-only adjustments cover package names, dependency aliases, publication metadata and provenance documentation. Application-specific integration belongs in consuming projects; the Quinn adapter here remains the upstream adapter with fork package wiring.
When upstream edits overlap, reconcile the implementation against the accepted upstream changes and retain the fork's package identity. Preserve released history and tags. Fork README files describe this distribution and link to upstream documentation rather than maintaining copies of it.
Report fork packaging or integration issues at iadev09/h3. Protocol fixes should be contributed upstream when applicable. See the release workflow for publication order and provenance.
License
MIT. Original copyright notices and contributor attribution are preserved.