Skip to main content

request-size-limit

request-size-limit

Enforces a maximum request body size: requests whose body exceeds max_bytes are rejected with a 413 through the node's error port. Place it early in the pipeline, before nodes that process the body or forward it upstream.

Configuration​

The single key is optional; the constructor never fails.

KeyTypeDefaultDescription
max_bytesinteger1048576 (1 MiB)Maximum allowed request body size in bytes.
type: request-size-limit
config:
  max_bytes: 262144

Behavior​

The request body is already fully buffered by the time a policy graph runs, so the plugin simply compares context.request.body length against max_bytes:

  • Within the limit — the request passes through the success port with the Context untouched.
  • Over the limit — the plugin writes a rejection onto context.response (status 413, JSON body {"error": "payload_too_large", "message": "Request body exceeds size limit"}, content-type: application/json) and fails with error code PAYLOAD_TOO_LARGE, routing the Context through the error port. The error message records the actual and allowed sizes (Body size <n> exceeds limit <max>), which an error-handler node can surface via {{error.message}}.

The plugin does not write to context.message.

UI editor note: the node inspector form also shows a reject_status field, but the plugin does not read that key — the rejection status is always 413.