[TASK] Throw PSR-7 Responses up to Application 66/57866/5
authorOliver Hader <oliver@typo3.org>
Fri, 10 Aug 2018 20:21:18 +0000 (22:21 +0200)
committerBenni Mack <benni@typo3.org>
Fri, 10 Aug 2018 21:38:04 +0000 (23:38 +0200)
commita959a3f87cc0895c10e73c74848bc8b4b5f1c36e
tree0dc19387e4ff09bee2b19a958a70810754905e70
parent5a8d6902dc90a7a30c2350fbf591eeb1f45d2403
[TASK] Throw PSR-7 Responses up to Application

In order to properly handle PSR-7 response objects explicit die()
or exit() calls should be avoided since those states cannot be
handle nor analyzed further. As a current work-around a new
ImmediateResponseException is introduced that throws the exception
up to application object that transforms the emitted message into
a proper response object. This API is internal and considered as
intermediate - the real solution would be to completely refactor
TypoScriptFrontendController processing and only use
request/response consequently.

Resolves: #85812
Releases: master
Change-Id: I047ad82fd5734c38160b8552aa754b1e7c356417
Reviewed-on: https://review.typo3.org/57866
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Frank Naegler <frank.naegler@typo3.org>
Tested-by: Frank Naegler <frank.naegler@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
composer.json
composer.lock
typo3/sysext/core/Classes/Http/AbstractApplication.php
typo3/sysext/core/Classes/Http/ImmediateResponseException.php [new file with mode: 0644]
typo3/sysext/core/composer.json
typo3/sysext/extbase/Tests/Functional/Persistence/TranslatedContentTest.php
typo3/sysext/fluid/Tests/Functional/View/TemplatesPathsTest.php
typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php
typo3/sysext/frontend/Tests/Functional/Rendering/LocalizedContentRenderingTest.php
typo3/sysext/frontend/Tests/Functional/Rendering/UriPrefixRenderingTest.php