---
title: "Breaking: #97550 - TypoScript option config.disableCharsetHeader removed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-97550-1651697278"
source: "Changelog/12.0/Breaking-97550-TypoScriptOptionConfigdisableCharsetHeaderRemoved.rst"
typo3-version: "12.0"
typo3-major: 12
type: "breaking"
issue: 97550
forge: "https://forge.typo3.org/issues/97550"
tags: ["TypoScript", "NotScanned", "ext:frontend"]
rendered: "2026-10-01T16:39:42+00:00"
---

# Breaking: #97550 - TypoScript option config.disableCharsetHeader removed {#breaking-97550-1651697278}

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

## Description {#description}

The TypoScript flag `config.disableCharsetHeader` has been completely removed
from TYPO3 Core.

This option was used to avoid sending HTTP headers of type `Content-Type` to
the client. This flag was mainly used to overcome a technical limitation to
override the Content-Type information back in TYPO3 v4.x.

## Impact {#impact}

TYPO3 now always sends the `Content-Type` header to the client in the TYPO3
Frontend.

## Affected installations {#affected-installations}

TYPO3 installations having this option enabled via TypoScript.

## Migration {#migration}

It is not needed to set this option. Even when Extbase plugins return JSON-based
Responses, the Content-Type header is already modified.

In special cases, when custom headers are required, it is possible to modify
the headers via a PHP-based PSR-15 middleware, or via TypoScript with
"config.additionalHeaders".