https://praxis.fast/praxis/v0.7.2/Recent content in Praxis Documentation on PraxisHugoenhttps://praxis.fast/praxis/v0.7.2/developing/adding-filters/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/adding-filters/Review the HTTP filter tutorial and extensions guide first.https://praxis.fast/praxis/v0.7.2/developing/adding-protocols/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/adding-protocols/Protocols translate between external network protocols and the internal filter pipeline.https://praxis.fast/praxis/v0.7.2/architecture/overview/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/overview/How Praxis combines protocol handling, filter pipelines, and upstream binding to build a configurable proxy.https://praxis.fast/praxis/v0.7.2/benchmarks/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/benchmarks/Praxis benchmark suites measure proxy throughput and latency alongside the cost of filter pipeline operations.https://praxis.fast/praxis/v0.7.2/architecture/body-buffering/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/body-buffering/How body chunks flow through the filter pipeline, how delivery modes interact, and how size limits layer.https://praxis.fast/praxis/v0.7.2/operating/build-features/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/build-features/Praxis is composed at build time with Cargo features.https://praxis.fast/praxis/v0.7.2/operating/capacity-planning/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/capacity-planning/Estimate file descriptor use from client and upstream connections, subrequests, DNS lookups, and configured connection limits before deployment.https://praxis.fast/praxis/v0.7.2/operating/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/configuration/Configure listeners, filter chains, upstream clusters, limits, administration, and runtime behavior with Praxis’s YAML file.https://praxis.fast/praxis/v0.7.2/architecture/connection-lifecycle/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/connection-lifecycle/Follow a client connection through accept, TLS setup, HTTP decoding, filter execution, and response delivery.https://praxis.fast/praxis/v0.7.2/architecture/crate-layout/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/crate-layout/praxis : Binary entry point. Loads YAML config, resolves per-listener filter chains into pipelines, registers protocol handlers, starts the server.https://praxis.fast/praxis/v0.7.2/developing/review-criteria/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/review-criteria/This document lists the criteria that matter most when deeply analyzing the Praxis codebase to find improvements.https://praxis.fast/praxis/v0.7.2/developing/dependencies/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/dependencies/Praxis keeps its dependency tree small, pinned, and auditable. This page documents the policy, the enforcement tooling, and a provenance review of every direct workspace dependency.https://praxis.fast/praxis/v0.7.2/developing/conventions/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/conventions/default unit of organization. Split code into small files with focused responsibilities.https://praxis.fast/praxis/v0.7.2/features/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/features/general-purpose provided builds, or extend your own custom proxy server using the Praxis framework.https://praxis.fast/praxis/v0.7.2/operating/fips/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/fips/Praxis does all of its cryptography in the system OpenSSL library.https://praxis.fast/praxis/v0.7.2/developing/fips/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/fips/Local checks that a praxis build is on track for FIPS 140-3 on Red Hat Enterprise Linux.https://praxis.fast/praxis/v0.7.2/developing/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/getting-started/signature verification and Red Hat’s scanner need Podman on Linux)https://praxis.fast/praxis/v0.7.2/operating/health-checking/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/health-checking/Praxis monitors upstream endpoint availability using active probes and passive observation. Unhealthy endpoints are automatically removed from load balancer rotation and restored when they recover.https://praxis.fast/praxis/v0.7.2/architecture/http-correctness/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/http-correctness/A proxy must enforce HTTP invariants that upstream servers and downstream clients may not. These are critical correctness and security concerns.https://praxis.fast/praxis/v0.7.2/architecture/life-of-a-request/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/life-of-a-request/This document traces a single HTTP request from arrival to response through the Praxis proxy.https://praxis.fast/praxis/v0.7.2/operating/load-balancing/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/load-balancing/Praxis distributes requests across upstream endpoints using configurable load-balancing strategies.https://praxis.fast/praxis/v0.7.2/operating/observability/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/observability/Praxis exposes Prometheus metrics, structured access logs, and health endpoints for monitoring proxy behavior. This guide covers setup, metric reference, logging configuration, and usage patterns.https://praxis.fast/praxis/v0.7.2/architecture/payload-processing/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/payload-processing/Filters declare body access needs at construction time via request_body_access(), response_body_access(), and the corresponding _body_mode() methods.https://praxis.fast/praxis/v0.7.2/architecture/pingora-handler-lifecycle/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/pingora-handler-lifecycle/This document describes how Praxis implements Pingora’s ProxyHttp trait to bridge the hook-based HTTP lifecycle into the Praxis filter pipeline.https://praxis.fast/praxis/v0.7.2/architecture/pipeline-concepts/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/pipeline-concepts/This document covers the pipeline system: how YAML configuration becomes a running filter pipeline, how filters communicate, and how conditional branching works.https://praxis.fast/praxis/v0.7.2/developing/project-management/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/project-management/All repositories in the praxis-proxy organization use a consistent workflow for planning, prioritizing, and tracking work.https://praxis.fast/praxis/v0.7.2/quickstart/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/quickstart/Build Praxis from source for local development, then route a request to an upstream backend.https://praxis.fast/praxis/v0.7.2/release/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/release/Praxis uses Semantic Versioning. The workspace version is the single source of truth, defined in workspace.package.version in the root Cargo.toml. All workspace crates inherit this version.https://praxis.fast/praxis/v0.7.2/operating/security-hardening/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/security-hardening/Security is a primary motivation of Praxis, not an afterthought. This guide covers the secure defaults and operational hardening for production deployments.https://praxis.fast/praxis/v0.7.2/architecture/tcp-proxy/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/tcp-proxy/Design of the raw TCP/L4 bidirectional forwarding protocol adapter.https://praxis.fast/praxis/v0.7.2/operating/tls/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/operating/tls/Configure downstream and upstream TLS for common listener and backend scenarios.https://praxis.fast/praxis/v0.7.2/developing/type-design/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/developing/type-design/Make invalid states unrepresentable. The type system and serde should enforce constraints at parse time, not at runtime.https://praxis.fast/praxis/v0.7.2/architecture/upstream-binding/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/v0.7.2/architecture/upstream-binding/A logical upstream binding pins one cluster to a request for the whole downstream request, so later filters can act on that cluster without running a second router.