Playground

Edit the rules and the request to see what the middleware would do with it. The page runs the library's matching logic in your browser: validation, path and method matching, expiry, and first-match-wins ordering.

Rules: the same JSON as PUT /rules

Rules are checked top to bottom. Move one up to see the first match change.

Request

GETPOSTPUTPATCHDELETE

GET /api/health GET /api/orders POST /api/orders GET /search GET /reports/q3

What it shows

• Validation: an invalid rule set is rejected as a whole, as PUT /rules would reject it with a 400 and keep the current rules.
• The trace: every rule checked, in order, and why it was skipped, until the first match.
• The response: the status, headers and body a shed request gets from the default responder.

Partial brownouts are random per request, so the playground shows the share that gets through rather than one outcome. ttl is accepted and treated as unexpired; set expires_at to a past time to see an expired rule skipped. See Rules for every field.