This project is mirrored from https://git.typo3.org/typo3/typo3.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- 14 Mar, 2018 1 commit
-
-
The change of \TYPO3\CMS\Core\Utility\GeneralUtility::getUrl() from cURL to GuzzleHttp the format of the $requestHeaders param was implicitly changed from an array of header strings to an associative array where the key is the header name and the value is either a single or an array of values for that header. This adds back support for the old list of headers format by detecting a non-associative array and converting it to the Guzzle key/value(s) style. At the same time the 'old' way is deprecated. Resolves: #84171 Related: #70056 Releases: master, 8.7 Change-Id: I41b23993957288dfd5294129fa8039aab717461d Reviewed-on: https://review.typo3.org/56046 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
- 15 Feb, 2018 1 commit
-
-
The goal is to decouple error handling from TSFE. For that, a new ErrorController is added which can be called and returns a Response object instead of exits the current request. In order to keep full backwards-compatibility, TSFE currently does not return a response, but instead exists with a response object. Next step: - Move the pageUnavailable_force functionality into a middleware - See what can be further abstracted to return a response Resolves: #83883 Releases: master Change-Id: I41f5f1a32a3f7edd48eb5c0464a26762ad4a946f Reviewed-on: https://review.typo3.org/55690 Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
-
