13 docs tagged with "middlewares"

All elements of Strapi's back end, like routes, policies, middlewares, controllers, services, models, requests, responses, and webhooks, can be customized.

In Strapi 5, the 'defaultIndex' option is removed from the 'public' middleware.

In Strapi 5, it's not recommended to update repeatable components with the Document Service API

With Strapi's error handling feature it's easy to send and receive errors in your application.

Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.

Middlewares alter the request or response flow at application or API levels. This documentation distinguishes global versus route middlewares and illustrates custom implementations with generation patterns.

Strapi offers a single entry point file for its middlewares configurations.

Existing plugins can be overriden by placing code in /src/extensions or using global register/bootstrap hooks. Instructions in this documentation cover reshaping plugin content-type schemas or server logic — altough upstream updates may break extensions.

Strapi policies are functions that execute specific logic on each request before it reaches the controller. Policies can be customized according to your needs.

Strapi routes handle requests to your content and are auto-generated for your content-types. Routes can be customized according to your needs.

Strapi's Server API for plugins allows a Strapi plugin to customize the back end part (i.e. the server) of your application.

The default log level of the middleware logger in Strapi 5 is 'http'.

Configure Strapi Cloud to use a third-party upload provider.