|
Orbit Framework 2.0.0
A high-performance asynchronous C++20 HTTP server framework.
|
Experimental. HTTP/3 has only been tested against Orbit's own test suite (libcurl with HTTP/3). It has not been checked against browsers, other HTTP/3 implementations or production traffic. Serve production traffic over HTTP/1.1 or HTTP/2, and expect behaviour and configuration to change. See Known Limitations.
Orbit can serve HTTP/3 over QUIC (UDP) itself, using ngtcp2 and nghttp3, next to its HTTP/1.1 and HTTP/2 listener.
HTTP/3 needs:
-DORBIT_ENABLE_HTTP3=ON (off by default; with vcpkg this also selects the http3 manifest feature, which brings in ngtcp2 and nghttp3), andThen select HTTP/3 with --http-version 3, or http_version in code:
Without a certificate, Orbit logs a warning and starts without QUIC. Remember to open the UDP port as well as the TCP port in firewalls and containers (see deployment.md).
Try it with a curl built with HTTP/3 support:
When HTTP/3 is enabled, App binds a UDP socket on the same port as the TCP listener and attaches a QuicConnectionManager to the first event loop. The manager runs the QUIC handshake and connections (ngtcp2), and QuicHttp3Session decodes HTTP/3 requests (nghttp3). Each request goes through the same Router as HTTP/1.1 and HTTP/2, so routes, middleware and error handlers are shared. Responses support bodies, files and streamed chunks.
event_loops > 1.Alt-Svc advertisement from the TCP listener, so browsers won't discover HTTP/3 on their own.