Bug #91380
closed
[FE][pageUnavailable_force] = true returns error code 500 instead of 503, skipping site handling
0%
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.
Updated by Jonathan Starck over 4 years ago
- Category set to Site Handling, Site Sets & Routing
- Target version set to next-patchlevel
- PHP Version set to 7.4
I can confirm the problem.
TYPO3 ignores the ErrorHandling on setting [FE][pageUnavailable_force].
Updated by Markus Klein over 4 years ago
- Related to Bug #91722: Maintenance Mode skips/ignore Error Handling added
Updated by Jonathan Starck about 4 years ago
I found this:
https://blog.t3bootstrap.de/2020/04/statische-routen-funktionieren-nicht/
Maybe it solves the Problem
Updated by Oliver Bartsch about 3 years ago
- Status changed from New to Needs Feedback
Hi, 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.
Updated by Rolf Kiefhaber about 3 years ago
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.
Updated by Oliver Bartsch about 3 years ago
- Status changed from Needs Feedback to Closed
Hi, 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.