HTTP protocol versions the library can actually use.
When set in KinetexRequest.httpVersion, the client attempts to use the specified version.
Falls back to the next available version if the requested version is unavailable:
HTTP/2 requires ALPN negotiation or h2 upgrade support
In most runtimes (Deno, Bun, Browser), HTTP/2 is negotiated automatically over TLS.
On Node.js, use createTransport with preferHTTP2: true for HTTP/2 support.
HTTP/3 is deliberately absent. As of this writing no runtime kinetex targets
ships an HTTP/3 client — Node's QUIC work is not in a stable release,
Deno's fetch has no HTTP/3, and Bun's node:quic is listen-only — so
offering the value let callers request something that silently came back as
HTTP/2. A server that advertises Alt-Svc: h3 is reported as HTTP/2,
which is the protocol the response was really served over.
HTTP protocol versions the library can actually use.
When set in KinetexRequest.httpVersion, the client attempts to use the specified version. Falls back to the next available version if the requested version is unavailable:
HTTP/2requires ALPN negotiation or h2 upgrade supportIn most runtimes (Deno, Bun, Browser), HTTP/2 is negotiated automatically over TLS. On Node.js, use createTransport with
preferHTTP2: truefor HTTP/2 support.HTTP/3is deliberately absent. As of this writing no runtime kinetex targets ships an HTTP/3 client — Node's QUIC work is not in a stable release, Deno'sfetchhas no HTTP/3, and Bun'snode:quicis listen-only — so offering the value let callers request something that silently came back as HTTP/2. A server that advertisesAlt-Svc: h3is reported asHTTP/2, which is the protocol the response was really served over.