TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #100189
Issue Bug Closed

#100189Content-Type charset is now also added for application/binary Extbase responses

Benni Mack 03/16/23, 22:24 updated 07/09/24, 12:46

Open in Forge Comment in Forge

Description

Since https://review.typo3.org/c/Packages/TYPO3.CMS/+/77158 the charset is now always added, and this actually breaks things,
if you return an Extbase Response that does not.

In TYPO3 v11 the mitigation is to set config.disableCharsetHeader = 1 in TypoScript, but this should be solved more elegantly.

Reviews 2

  • 11.5 78171[BUGFIX] Only set Content-Type charset if no charset is given Resolves this issue Merged Benni Mack CR +2 V +2 → main Easy +5 −3 03/29/23, 07:09
  • main 78132[BUGFIX] Only set Content-Type charset for text/html or JSON Resolves this issue Merged Benni Mack CR +2 V +2 → 11.5 Easy +3 −5 03/19/23, 14:19

Related issues 3

  • Task #97550Remove config.disableCharsetHeader Related to Closed Frontend v12 Benni Mack 05/04/22, 20:39
  • Bug #99373HTTP Header Content-Type not set when Extbase action is cached Related to Closed Extbase v12 Helmut Hummel 12/14/22, 17:49
  • Bug #99534Content-Type forced to text/html when streaming file Related to Closed v11 Gregor Hermens 01/13/23, 13:00
Assigned to
Benni Mack
Author
Benni Mack
Priority
Should have
Category
Frontend
Target version
Candidate for patchlevel
TYPO3 version
11
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback