---
title: "Deprecation: #94394 - Extbase Request setDispatched() and isDispatched()"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-94394"
source: "Changelog/11.3/Deprecation-94394-ExtbaseRequestSetDispatchedAndIsDispatched.rst"
typo3-version: "11.3"
typo3-major: 11
type: "deprecation"
issue: 94394
forge: "https://forge.typo3.org/issues/94394"
tags: ["PHP-API", "FullyScanned", "ext:extbase"]
rendered: "2026-09-24T12:29:17+00:00"
---

# Deprecation: #94394 - Extbase Request setDispatched() and isDispatched() {#deprecation-94394}

See [forge#94394](https://forge.typo3.org/issues/94394)

## Description {#description}

To further prepare towards PSR-7 requests in Extbase, the two
methods `\TYPO3\CMS\Extbase\Mvc\Request->setDispatched()` and
`\TYPO3\CMS\Extbase\Mvc\Request->isDispatched()` have been
marked as deprecated.

## Impact {#impact}

Using the methods is discouraged. The Extbase dispatcher still
recognizes them and acts accordingly, the methods do **not** raise
a deprecation level log entry, though.

## Affected Installations {#affected-installations}

Some Extbase based extensions may use `setDispatched()`, but
it's rather unlikely since that flag has been mostly used internally
through existing helper methods in Extbase controllers.

The extension scanner will find possible candidates.

## Migration {#migration}

Action dispatching in Extbase now depends on the returned response:

-   A casual 2xx Response from a controller action that for instance contains HTML
    or Json stops Extbase dispatching, the response is later returned to the client.
-   An Extbase `ForwardResponse` instructs the dispatcher to dispatch
    internally to another controller action.
-   A 3xx `RedirectResponse` stops dispatching and is returned to the client
    to initiate some client redirect.