litestar-middleware

Apply Litestar middleware using a configuration-first approach for built-in concerns like CORS, rate limiting, and CSRF. Attach these components at the application, router, controller, or handler layer to enforce policies globally or selectively across routes.

Add request logging to a Litestar API by attaching logging middleware across application and router layers. This centralizes behavior for all incoming requests, ensuring consistent logging without adding code to individual route handlers.

Use ASGIMiddleware, MiddlewareProtocol, or AbstractMiddleware in Litestar when built-in configurations cannot meet your requirements. These base classes allow safe customization of cross-cutting behavior while maintaining correct middleware call order across application and router layers.

Yes, Litestar middleware supports layer-aware attachment across application, router, controller, and handler levels. You can apply global policies like CSRF protection at the app level while targeting compression or rate limiting to specific router layers.

The best way to enforce security headers across many Litestar routes is attaching middleware at the application layer. This centralizes policy enforcement for all requests without duplicating logic in individual controllers or handlers.

Litestar middleware call order matters because layers execute sequentially, affecting how cross-cutting concerns like rate limiting and logging interact. Correct attachment at application, router, and controller layers ensures policies are applied in the intended safe sequence.