---
title: "Deprecation: #99650 - Global Request object usage in Extbase UriBuilder"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-99650-1674205203"
source: "Changelog/12.2/Deprecation-99650-ExtbaseUriBuilderGlobalRequest.rst"
typo3-version: "12.2"
typo3-major: 12
type: "deprecation"
issue: 99650
forge: "https://forge.typo3.org/issues/99650"
tags: ["PHP-API", "FullyScanned", "ext:core"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Deprecation: #99650 - Global Request object usage in Extbase UriBuilder {#deprecation-99650-1674205203}

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

## Description {#description}

Usage of the global request object (`$GLOBALS['TYPO3_REQUEST']`) as
fallback in the EXT:extbase `\TYPO3\CMS\Extbase\Mvc\Web\Routing\UriBuilder`
has been deprecated and will be removed in TYPO3 v13. The `UriBuilder` will
then solely rely on a locally set request object.

## Impact {#impact}

Using the `UriBuilder` class of Extbase without a local
request object will trigger a PHP deprecation warning.

Additionally, when using the `UriBuilder` to build frontend URLs, the
current content object is required. It is initialized from the handed in local
request object. This means, in case extensions do set the request object,
a automatic fallback is applied in v12, triggering a PHP deprecation warning, as
it will be removed in v13, too.

## Affected installations {#affected-installations}

TYPO3 installations with custom extensions initializing the `UriBuilder`
without handing in a request object and using it to build URIs.

## Migration {#migration}

Make sure to call `setRequest($request)` before using the
`UriBuilder`, when no other component has done this already.

Using ViewHelpers will not trigger the warning, as the TYPO3 Core ensures
the proper setup.