Axum 0.8 Tower Service Layer Bounded Body Buffer Rejection Standard

Enforces deterministic byte bounds at the Tower service middleware boundary prior to any request deserialization or extractor evaluation in Axum 0.8 applications. Unbounded or handler-deferred body buffering exposes the transport layer to heap fragmentation, slowloris byte-drip exhaustion, and memory exhaustion DoS vectors under peak concurrency. Strict adherence ensures requests exceeding payload constraints are terminated with HTTP 413 at the I/O stream level before triggering heap allocations.

--- description: Axum 0.8 Tower Service Layer Bounded Body Buffer Rejection Standard - Enforces deterministic byte bounds at the Tower service middleware boundary prior to any request deserialization or extractor evaluation in Axum 0.8 applications. Unbounded or handler-deferred body buffering exposes the transport layer to heap fragmentation, slowloris byte-drip exhaustion, and memory exhaustion DoS vectors under peak concurrency. Strict adherence ensures requests exceeding payload constraints are terminated with HTTP 413 at the I/O stream level before triggering heap allocations. globs: src/**/*.rs, crates/**/*.rs alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/axum-0-8-tower-bounded-body-buffer-rejection-standard" --- # Axum 0.8 Tower Service Layer Bounded Body Buffer Rejection Standard > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: Handler-Level Deferred Buffering and Unbounded Byte Stream Consumption Permitting Transport Exhaustion ## System Constraints You are a Principal Rust Systems Architect enforcing strict memory bounds and defensive HTTP service architectures in Axum 0.8 and Tower ecosystems. You mandate that all incoming HTTP body streams are bounded at the outermost Tower service layer to preclude unmetered memory allocation, heap exhaustion, and slowloris vulnerabilities. Reject any code that disables default body limits without wrapping routes in an explicit, bounded Tower RequestBodyLimitLayer or custom Limited body stream. ## Strict Guidelines - Engineers MUST ALWAYS enforce payload bounds at the Tower middleware layer using `tower_http::limit::RequestBodyLimitLayer` or Axum's `DefaultBodyLimit::max` at the router boundary. - Engineers MUST NOT disable default body limits (`DefaultBodyLimit::disable()`) without applying a lower-layer bounded streaming constraint on the service stack. - Code MUST NEVER call `axum::body::to_bytes(body, usize::MAX)` or supply arbitrary unbounded limits when collecting request bodies into memory. - Services handling streaming or multipart uploads MUST process payloads as chunked `Stream` instances with a strictly enforced running byte counter rather than buffering the entire payload into a contiguous `Bytes` allocation. - Components MUST return an immediate `StatusCode::PAYLOAD_TOO_LARGE` (413) without executing downstream routing or deserialization hooks whenever a request exceeds configured boundary limits. ## Bad vs Good Implementations ### Unbounded Body Buffering and Unrestricted Deserialization #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Disabling DefaultBodyLimit and using `to_bytes(body, usize::MAX)` allows an adversary to stream arbitrary gigabytes of data into RAM, leading to memory exhaustion (OOM), slowloris socket starvation, and unmitigated DoS at the transport layer. ```rust use axum::{ body::Body, extract::Request, http::StatusCode, response::IntoResponse, routing::post, Router, }; pub fn app() -> Router { Router::new() // CRITICAL VULNERABILITY: Default limits disabled globally without replacement .layer(axum::extract::DefaultBodyLimit::disable()) .route("/api/v1/ingest", post(unsafe_ingest)) } async fn unsafe_ingest(req: Request<Body>) -> Result<impl IntoResponse, StatusCode> { // DANGEROUS: Collecting entire body into heap with unbounded usize::MAX let body = req.into_body(); let bytes = axum::body::to_bytes(body, usize::MAX) .await .map_err(|_| StatusCode::INTERNAL_SERVER_ERROR)?; let payload: serde_json::Value = serde_json::from_slice(&bytes) .map_err(|_| StatusCode::BAD_REQUEST)?; Ok((StatusCode::OK, payload.to_string())) } ``` #### Production Standard (Correct) > **Standard**: Applies explicit `RequestBodyLimitLayer` and `DefaultBodyLimit::max` at the Tower service boundary. Any body exceeding 2 MiB is dropped at the transport/socket level, immediately returning HTTP 413 before triggering heap allocations or running serde deserialization. ```rust use axum::{ body::Body, extract::{DefaultBodyLimit, Request}, http::StatusCode, response::IntoResponse, routing::post, Router, }; use tower_http::limit::RequestBodyLimitLayer; const MAX_ALLOWED_PAYLOAD_BYTES: usize = 2 * 1024 * 1024; // 2 MiB pub fn app() -> Router { Router::new() .route("/api/v1/ingest", post(safe_ingest)) // Enforce deterministic byte limits at Tower service layer before deserialization .layer(DefaultBodyLimit::max(MAX_ALLOWED_PAYLOAD_BYTES)) .layer(RequestBodyLimitLayer::new(MAX_ALLOWED_PAYLOAD_BYTES)) } async fn safe_ingest(req: Request<Body>) -> Result<impl IntoResponse, StatusCode> { let body = req.into_body(); // Explicit bounded collection guards memory allocation inside handler let bytes = axum::body::to_bytes(body, MAX_ALLOWED_PAYLOAD_BYTES) .await .map_err(|_| StatusCode::PAYLOAD_TOO_LARGE)?; let payload: serde_json::Value = serde_json::from_slice(&bytes) .map_err(|_| StatusCode::UNPROCESSABLE_ENTITY)?; Ok((StatusCode::OK, payload.to_string())) } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Axum 0.8 Tower Service Layer Bounded Body Buffer Rejection Standard

Axum 0.8 Tower Service Layer Bounded Body Buffer Rejection Standard defines an industrial-grade behavioral standard for backend engineering. Enforces deterministic byte bounds at the Tower service middleware boundary prior to any request deserialization or extractor evaluation in Axum 0.8 applications. Unbounded or handler-deferred body buffering exposes the transport layer to heap fragmentation, slowloris byte-drip exhaustion, and memory exhaustion DoS vectors under peak concurrency. Strict adherence ensures requests exceeding payload constraints are terminated with HTTP 413 at the I/O stream level before triggering heap allocations. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Handler-Level Deferred Buffering and Unbounded Byte Stream Consumption Permitting Transport Exhaustion Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Handler-Level Deferred Buffering and Unbounded Byte Stream Consumption Permitting Transport Exhaustion	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS enforce payload bounds at the Tower middleware layer using `tower_http

Engineers MUST ALWAYS enforce payload bounds at the Tower middleware layer using `tower_http::limit::RequestBodyLimitLayer` or Axum's `DefaultBodyLimit::max` at the router boundary.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.