Path-based routes
Match HTTP request paths to upstream destinations.
Read in the docsRoute HTTP requests by path, send traffic to TCP and UDP targets, and apply configurable request policies.
How a request flows
Forward HTTP requests using configured paths, or proxy TCP and UDP traffic through their own listeners.
Match HTTP request paths to upstream destinations.
Read in the docsDistribute requests across multiple configured servers with failover.
Read in the docsForward stream traffic from dedicated listeners to configured targets.
Read in the docsSet listener, routing, and request behavior in YAML and override selected values through the environment.
Define server options, timeouts, upstreams, and optional watcher behavior.
Read in the docsConfigure rate limits, API keys, JWT, CIDR rules, method and path rules, and body limits.
Read in the docsConfigure listener TLS, optional mTLS, and Redis for the global HTTP rate limiter.
Read in the docsRun the proxy and inspect built-in health and metrics endpoints.
Check whether the process responds and whether HTTP upstreams are ready.
Read in the docsExpose HTTP request and response metrics at the built-in endpoint.
Read in the docsOptionally sample process memory and write reports when the configured threshold is reached.
Read in the docs| Capability | Configuration | Applies to |
|---|---|---|
| Path routing | upstream[].path | HTTP requests |
| Upstream pool | upstream[].servers | HTTP routes |
| Stream listener | protocol, listen, server_url | TCP and UDP entries |
| Access policies | upstream[].security | HTTP routes |