Protocol

Choose your HTTP protocol version — HTTP/1.1, HTTP/2, or HTTP/3 with QUIC. tgrs supports protocol racing for optimal performance.

Protocol Versions

Force a Specific Protocol

By default, tgrs automatically negotiates the best protocol. Use these flags to force a specific version.

# Force HTTP/1.1

tgrs GET https://api.example.com/data --http1.1

# Force HTTP/2

tgrs GET https://api.example.com/data --http2

# Force HTTP/3 (QUIC)

tgrs GET https://api.example.com/data --http3

Protocol Racing

Automatic Protocol Selection

By default, tgrs uses protocol racing — it tries HTTP/3 (QUIC) and HTTP/2 simultaneously and uses whichever responds first. This gives you the fastest connection without manual configuration.

# Default behavior: protocol racing enabled

tgrs GET https://api.example.com/data

The fallback order is: HTTP/3 → HTTP/2 → HTTP/1.1. Use protocol flags above to force a specific version.

Certificate Info

TLS Certificate Details

Use -C / --cert-info to inspect the server's TLS certificate — subject, issuer, validity dates, key type, and algorithms.

tgrs GET https://api.example.com/data -C

tgrs GET https://api.example.com/data --cert-info

Quick Reference

Protocol Flags

FlagDescription
--http1.1Force HTTP/1.1
--http2Force HTTP/2
--http3Force HTTP/3 (QUIC)
-C, --cert-infoShow TLS certificate details