---
title: "Deprecation: #94231 - Extbase InvalidRequestMethodException"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-94231"
source: "Changelog/11.3/Deprecation-94231-DeprecateExtbaseInvalidRequestMethodException.rst"
typo3-version: "11.3"
typo3-major: 11
type: "deprecation"
issue: 94231
forge: "https://forge.typo3.org/issues/94231"
tags: ["PHP-API", "FullyScanned", "ext:extbase"]
rendered: "2026-09-17T21:17:42+00:00"
---

# Deprecation: #94231 - Extbase InvalidRequestMethodException {#deprecation-94231-extbase-invalidrequestmethodexception}

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

## Description {#description}

To further prepare towards PSR-7 Requests in Extbase, the
`\TYPO3\CMS\Extbase\Mvc\Request` has to be streamlined.

Therefore, the internal method `setMethod()` has been removed.
This method previously threw the `InvalidRequestMethodException`.
Since this was the only usage and the exception is not used within
TYPO3 / Extbase anymore, the exception is deprecated.

## Impact {#impact}

Using `\TYPO3\CMS\Extbase\Mvc\Exception\InvalidRequestMethodException`
in custom extension code is discouraged since it will be removed with TYPO3
v12 and is also no longer thrown by TYPO3.

## Affected Installations {#affected-installations}

Extbase based extensions may manually throw or catch
`\TYPO3\CMS\Extbase\Mvc\Exception\InvalidRequestMethodException`.
The extension scanner will find those usages.

## Migration {#migration}

All usages of `\TYPO3\CMS\Extbase\Mvc\Exception\InvalidRequestMethodException`
in custom extension code, which is very unlikely, have to be replaced with a
custom exception, if needed at all.