Struct RequestValidationPlugin 

pub struct RequestValidationPlugin {
    header_schema: Option<Validator>,
    body_schema: Option<Validator>,
    conditions: Option<Expr>,
    rejected_code: u16,
    rejected_msg: Option<Template>,
}

Validates context.request headers and body against compiled JSON Schemas, and optionally evaluates boolean condition predicates on the request. On failure the request is rejected through the denied port with a JSON response using rejected_code.

Headers are validated as a single-value object (first value per header, names lowercased), matching the shape APISIX passes to its schema check. After a successful JSON-body validation the body is re-serialized from the parsed document, so the JSON that was validated is exactly the JSON the upstream receives (guards against JSON-interoperability smuggling).

Fields

header_schema: Option<Validator>

body_schema: Option<Validator>

conditions: Option<Expr>

rejected_code: u16

rejected_msg: Option<Template>

Fixed message returned instead of the validator’s error description. Supports {{namespace.path}} references (no legacy $var interpolation — this field never supported it, so this sweep must not start).

Implementations

impl RequestValidationPlugin

pub fn from_config(config: &HashMap<String, Value>) -> Result<Self, String>

Builds the plugin from node config.

Accepted keys:

• header_schema (object): JSON Schema applied to the request headers, seen as {name: first_value} with lowercase names.
• body_schema (object): JSON Schema applied to the parsed request body (JSON, or urlencoded decoded to a flat object).
• conditions (array): a condition expression (see crate::vars::Expr) — rules ANDed at top level, nested AND/OR/NOT groups, JSONPath body subjects. Evaluated after the schemas; failure rejects like a schema failure with message “request conditions not satisfied”.
• rejected_code (integer 200–599, default 400): response status for rejected requests.
• rejected_msg (string): fixed message returned instead of the validator’s error description. Supports {{namespace.path}} references.

At least one of header_schema, body_schema, or conditions is required; schemas are compiled here so malformed schemas fail at config load.

type: request-validation
config:
  rejected_code: 422
  body_schema:
    type: object
    required: [name]
    properties:
      name: { type: string, minLength: 1 }

fn reject( &self, ctx: Context, detail: String, ) -> Result<PluginOutput, PluginExecutionError>

Writes the rejection onto the response and routes the context through the node’s denied port.

Trait Implementations

impl Debug for RequestValidationPlugin

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

Formats the value using the given formatter.

impl Plugin for RequestValidationPlugin

fn plugin_type(&self) -> &str

Unique identifier for the plugin type (e.g., “proxy-rewrite”, “upstream”). This is also the key its PortSpec is registered under in port_spec.

fn execute<'life0, 'async_trait>( &'life0 self, ctx: Context, ) -> Pin<Box<dyn Future<Output = Result<PluginOutput, PluginExecutionError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Executes the plugin logic against the request/response context.

fn reads_response_body(&self) -> bool

Whether this configured instance reads context.response.body.

fn cache_target(&self) -> Option<CacheTarget>

The cache backend this node writes to, if it is a proxy-cache half.