#91380[FE][pageUnavailable_force] = true returns error code 500 instead of 503, skipping site handling
Description
When setting the [FE][pageUnavailable_force] option to true, a default Typo3 error page is returned with a 500 error code header.
This happened with a freshly installed Typo3 10 with PHP 7.2, 7.3, or 7.4. Typo3 9 returned a 503 header as expected.
Setting this option also skips the site handling, so it is impossible to set a custom maintenance page, because the error is returned before site handling is executed. The default error page is returned even if a error handler for 0 is defined.
I don’t know, if this is because of the 500 header or in addition to it.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 7
-
Jonathan Starck commented and changed category target version PHP Version 7.4 06/29/20, 01:28
-
Jonathan Starck commented 06/29/20, 01:48
#91722
-
Markus Klein changed Related to #91722 06/29/20, 09:14
-
Jonathan Starck commented 10/18/20, 06:45
I found this:
https://blog.t3bootstrap.de/2020/04/statische-routen-funktionieren-nicht/Maybe it solves the Problem
-
Oliver Bartsch commented and changed status
NewNeeds Feedback 10/12/21, 20:12Hi, do you still encounter this bug?
I tested with latest matser and 10.4 – in both cases I correctly receive the 503 status code after setting
pageUnavailable_force => true. -
Rolf Kiefhaber commented 10/13/21, 05:39
I just tested on Typo3 10.4.21 and I get the 503 Maintenance Page now. Seems like on of the patch versions fixed it.
-
Oliver Bartsch commented and changed status
Needs FeedbackClosed 10/13/21, 09:28Hi, thanks for the feedback. Therefore, I close this issue now. In case you encounter this issue again, please create a new issue with reference to this one.
I can confirm the problem.
TYPO3 ignores the ErrorHandling on setting [FE][pageUnavailable_force].