You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A one-screen, legend-coded map of what ExpressGateway supports, what is gated
off, what is waived, and what is deferred. Every row points at the page that
owns the detail — this page is the index, not the explanation.
The bounded why behind every gated/waived/deferred item lives in
../known-limitations.md (with a "who does this
affect?" note on each).
The protocol matrix and feature detail live in
../features.md.
Every config knob and its reload class live in CONFIG.md.
Legend: ✅ supported · ⛔ gated off by default · ☑️ opt-in · ⚠️ bounded
limitation · ⏳ deferred / not yet characterized.
HTTP protocol matrix (front × back)
The full 9-cell matrix — any of {H1, H2, H3} on the client side translated to
any of {H1, H2, H3} on the backend — streamed frame-by-frame with bounded memory
(64 MiB caps + 413). Front protocol is the listenerprotocol; back
protocol is the per-backendprotocol. H2 is served on an h1s listener via
ALPN; H3 on a quic listener. Detail: ../features.md.
The security audit closed at 0 Critical / 0 High / 1 Medium (fixed) / 7 Low / 4
Info. Production wire parsing is delegated to hyper (H1/H2), quiche/BoringSSL
(H3/QUIC/TLS), rustls (TLS), and tungstenite (WS); the only hand-rolled
production parser is the Mode A QUIC public-header reader, which is panic-free by
construction and was fuzzed extensively. Full record:
../../SECURITY.md.