litestar-org Litestar Middleware
Use this skill for built-in middleware config, custom ASGI middleware, request lifecycle hooks, and auth user loading.
Code Style Rules
- Use built-in middleware configs before custom middleware.
- Keep middleware focused on cross-cutting request behavior.
- Filter by ASGI scope when middleware applies only to HTTP or WebSocket.
- Keep business policy in Guards and services.
Quick Reference
- Middleware patterns: middleware.md
- Pair with litestar-auth-guards for permission checks.
- Pair with litestar-deployment for proxy and platform concerns.
Workflow
- Decide whether a built-in config solves the need.
- Choose custom middleware only for cross-cutting behavior.
- Set ordering deliberately.
- Verify HTTP and WebSocket behavior separately when both apply.
Guardrails
- Do not put business workflows in middleware.
- Do not apply HTTP-only middleware to WebSocket scopes.
- Do not mutate request state without documenting the key.
- Do not duplicate Guard policy in middleware.
Validation Checkpoint
- Middleware order is intentional.
- Scope filtering is correct.
- Built-in configs are used where available.
- Tests cover the request path affected by middleware.
Example
from litestar.middleware import ASGIMiddleware
middleware = [RequestIDMiddleware()]
References Index
- middleware.md
Official References
- https://docs.litestar.dev/ - Litestar documentation
- https://docs.litestar.dev/latest/reference/ - Litestar API reference