Project

General

Profile

Actions

Bug #99032

open

Multiple Set-Cookie-Headers in Extbase-Responses are not sent to browser

Added by Markus Müller-Wipperfürth about 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
Start date:
2022-11-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
7.4
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:
Stabilization Sprint

Description

If I add multiple HTTP-headers with the same name (e.g. "Set-Cookie") in Extbase-Controllers by adding them to the PSR-(Extbase-)Response, only the last one is sent to the browser.

The problem occurs in TYPO3\CMS\Extbase\Core\Bootstrap in line 202, when calling the header()-Method without making a difference if headers with multiple values should be replaced or added. Because of this behaviour, only the last Cookie is sent the the browser, because the last "Set-Cookie" overrides the previous one.

An identical problem existed in TYPO3 Core PSR-Responses, but was already fixed (see: https://forge.typo3.org/issues/88482).
This solution could also be adopted to Extbase to fix the described problem.


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #88482: Allow multi line headers for "Set-Cookie" headersClosed2019-06-03

Actions
Related to TYPO3 Core - Bug #105591: ext:felogin does not delete fe_typo_user Cookie on logoutNewTorben Hansen2024-11-13

Actions
Actions #1

Updated by Markus Müller-Wipperfürth about 2 years ago

  • Related to Bug #88482: Allow multi line headers for "Set-Cookie" headers added
Actions #2

Updated by Benni Mack over 1 year ago

  • Sprint Focus set to Stabilization Sprint
Actions #3

Updated by Benni Mack 7 days ago

  • Related to Bug #105591: ext:felogin does not delete fe_typo_user Cookie on logout added
Actions

Also available in: Atom PDF