Project

General

Profile

Actions

Bug #100189

closed

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

Added by Benni Mack about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
Frontend
Start date:
2023-03-16
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

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.


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #99373: HTTP Header Content-Type not set when Extbase action is cachedClosed2022-12-14

Actions
Related to TYPO3 Core - Task #97550: Remove config.disableCharsetHeaderClosedBenni Mack2022-05-04

Actions
Related to TYPO3 Core - Bug #99534: Content-Type forced to text/html when streaming fileClosed2023-01-13

Actions
Actions

Also available in: Atom PDF