Struct RequestLimits 

pub struct RequestLimits {
    pub max_body_bytes: Option<u64>,
    pub max_header_count: Option<u32>,
    pub max_header_bytes: Option<u64>,
    pub dry_run: bool,
}

Route-scoped request size limits (DW-027, feature analysis 4.16).

Semantics (frozen; enforcement lives in dataplane::hardening):

• Header limits (max_header_count, max_header_bytes) are checked immediately after route resolution, before CORS preflight handling and authentication; a violation answers 431 with the JSON error envelope. max_header_bytes is the SUM of all header name and value bytes of the request (hyper’s per-connection buffer limits still apply beneath this, process-wide).
• max_body_bytes: a request whose Content-Length declares more is rejected 413 before any upstream contact. A body of UNKNOWN length (chunked / h2 without content-length) is wrapped in a counting guard: crossing the cap aborts the request (the upstream attempt fails; the client receives 413 when the failure precedes the upstream’s response headers, a torn stream otherwise).
• A block with NO field set is rejected by validation (always an authoring mistake; omit the block).

Fields

max_body_bytes: Option<u64>

Maximum request body size in bytes (declared via Content-Length or enforced streaming). Absent: unlimited.

max_header_count: Option<u32>

Maximum number of header fields on the request. Absent: unlimited (hyper’s parser bound applies).

max_header_bytes: Option<u64>

Maximum total size of request headers (names + values, bytes). Absent: unlimited.

dry_run: bool

Monitor mode (DW-041): evaluate the limits, LOG and count every would-be rejection (dwara_policy_dry_run_total{phase="route_ limits"} + a dwara::policy warn event), but let the request PROCEED — including its body: the streaming max_body_bytes guard is not armed, so a chunked body that would have been aborted mid- stream streams through (only the cheap up-front checks — header count/bytes, a declared Content-Length — are observable in dry run). The staging tool for turning limits on against live traffic without breaking clients.

Trait Implementations

impl Clone for RequestLimits

fn clone(&self) -> RequestLimits

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RequestLimits

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for RequestLimits

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for RequestLimits

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl PartialEq for RequestLimits

fn eq(&self, other: &RequestLimits) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for RequestLimits

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl Copy for RequestLimits

impl Eq for RequestLimits

impl StructuralPartialEq for RequestLimits