<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protocols on Praxis</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/</link><description>Recent content in Protocols on Praxis</description><generator>Hugo</generator><language>en</language><atom:link href="https://praxis.fast/praxis/dev/examples/configs/protocols/index.xml" rel="self" type="application/rss+xml"/><item><title>Grpc Http2 Upstream</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/grpc-http2-upstream.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/grpc-http2-upstream.yaml/</guid><description>Praxis proxies to upstreams over HTTP/1.1 by default. gRPC backends speak HTTP/2 only, and a call&amp;rsquo;s outcome (grpc-status) arrives in response trailers, which no HTTP/1.1 leg can carry</description></item><item><title>Mixed Protocol</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/mixed-protocol.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/mixed-protocol.yaml/</guid><description>HTTP and TCP listeners run on a single server instance</description></item><item><title>Tcp Consistent Hash</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-consistent-hash.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-consistent-hash.yaml/</guid><description>TCP consistent-hash load balancing (client IP affinity)</description></item><item><title>Tcp Least Connections</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-least-connections.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-least-connections.yaml/</guid><description>TCP least-connections load balancing</description></item><item><title>Tcp Proxy</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-proxy.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-proxy.yaml/</guid><description>Bidirectional TCP forwarding</description></item><item><title>Tcp Round Robin</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-round-robin.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-round-robin.yaml/</guid><description>TCP round-robin load balancing across database replicas</description></item><item><title>Tcp Timeouts</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-timeouts.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-timeouts.yaml/</guid><description>TCP proxy with session and max duration timeouts. tcp_session_timeout_ms wraps the entire TCP forwarding session in a hard deadline, terminating connections after the threshold regardless of activity. tcp_max_duration_secs caps the total session duration in seconds</description></item><item><title>Tcp Tls Mtls</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-tls-mtls.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-tls-mtls.yaml/</guid><description>The proxy requires TCP clients to present a valid TLS certificate signed by the trusted CA</description></item><item><title>Tcp Tls Termination</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-tls-termination.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tcp-tls-termination.yaml/</guid><description>TLS on the listener; plain TCP to the upstream backend</description></item><item><title>Tls Cipher Suites</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-cipher-suites.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-cipher-suites.yaml/</guid><description>Restrict accepted cipher suites per listener</description></item><item><title>Tls Http Reencrypt</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-http-reencrypt.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-http-reencrypt.yaml/</guid><description>HTTPS on the listener; TLS to the upstream backend</description></item><item><title>Tls Mtls Both</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-both.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-both.yaml/</guid><description>Client mTLS to the proxy (client cert required), and proxy mTLS to the upstream backend (proxy presents its own client certificate)</description></item><item><title>Tls Mtls Listener</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-listener.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-listener.yaml/</guid><description>The proxy requires clients to present a valid TLS certificate signed by the trusted CA</description></item><item><title>Tls Mtls Listener Request</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-listener-request.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-listener-request.yaml/</guid><description>The proxy requests a client certificate but does not require one</description></item><item><title>Tls Mtls Spiffe</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-spiffe.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-spiffe.yaml/</guid><description>The proxy authorizes a client at the TLS handshake by the SPIFFE ID in its X.509-SVID client certificate</description></item><item><title>Tls Mtls Upstream</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-upstream.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-mtls-upstream.yaml/</guid><description>Plain HTTP from clients; the proxy presents a client certificate to the upstream backend, which requires mutual TLS authentication</description></item><item><title>Tls Multi Cert</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-multi-cert.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-multi-cert.yaml/</guid><description>Multiple certificates on one listener; Praxis selects the certificate matching the client&amp;rsquo;s SNI hostname</description></item><item><title>Tls Sni Routing</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-sni-routing.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-sni-routing.yaml/</guid><description>Routes TLS connections to different upstreams based on the Server Name Indication (SNI) hostname in the ClientHello</description></item><item><title>Tls Termination</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-termination.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-termination.yaml/</guid><description>Accept HTTPS connections and forward decrypted requests to an HTTP backend.</description></item><item><title>Tls Verify Disabled</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-verify-disabled.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-verify-disabled.yaml/</guid><description>Plain HTTP listener; TLS to the upstream with certificate verification disabled</description></item><item><title>Tls Version Constraint</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-version-constraint.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/tls-version-constraint.yaml/</guid><description>Restrict accepted TLS versions via min_version</description></item><item><title>Upstream Ca File</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/upstream-ca-file.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/upstream-ca-file.yaml/</guid><description>Sets a trusted CA bundle for all upstream TLS connections via runtime.upstream_ca_file</description></item><item><title>Upstream Tls</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/upstream-tls.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/upstream-tls.yaml/</guid><description>Plain HTTP on the listener; TLS to the upstream</description></item><item><title>Websocket</title><link>https://praxis.fast/praxis/dev/examples/configs/protocols/websocket.yaml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/praxis/dev/examples/configs/protocols/websocket.yaml/</guid><description>HTTP listener that transparently proxies WebSocket upgrade requests</description></item></channel></rss>