---
title: "Extbase in middlewares"
manual: "TYPO3 Explained"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3coreapi:extbase-no-frontend-middleware@main"
source: "ExtensionArchitecture/Extbase/NoFrontendContext/Middleware.rst"
rendered: "2026-09-26T10:15:30+00:00"
---

# Extbase in middlewares {#extbase-no-frontend-middleware}

> [!NOTE]
> This page is a work in progress. Content will be added as part of the
> Extbase documentation overhaul.

Middlewares inspect and modify the request and response: adding headers,
short-circuiting with a redirect, answering a route directly. Extensions
sometimes want domain data at that point like an API endpoint or a conditional
redirect based on a record.

Whether Extbase can provide it depends entirely on where in the chain the
middleware runs.

The essentials:

-   The site, the language and the frontend TypoScript configuration are
    established by the frontend middleware chain. A middleware running before
    that point has none of them, and Extbase cannot resolve its configuration.
-   A middleware running after the frontend has been prepared has all of it.
    The resolved site and language are available as request attributes, and
    can be tested for rather than assumed.
-   A middleware ordered without constraints may run anywhere in the chain, so
    one that depends on the frontend having been prepared has to say so in its
    registration.
-   Needing to establish a context before Extbase works is a sign the work may
    belong elsewhere: in a plugin behind a route enhancer, in a service called
    from a controller, or expressed directly against the
    [database API](https://docs.typo3.org/permalink/t3coreapi:database@main).

> [!WARNING]
> Do not reference the internal middlewares of the frontend chain by name
> when ordering your own. Several of them, including the one that prepares
> frontend rendering, are marked internal and may be renamed or removed.

> [!NOTE]
> **See also**
>
> [Middlewares (request handling)](https://docs.typo3.org/permalink/t3coreapi:request-handling@main) for the middleware
> chain and how middlewares are registered and ordered.