Bug #91380

[FE][pageUnavailable_force] = true returns error code 500 instead of 503, skipping site handling

Added by Rolf Kiefhaber over 1 year ago. Updated about 2 months ago.

Should have
Link Handling, Site Handling & Routing
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


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.

Related issues

Related to TYPO3 Core - Bug #91722: Maintenance Mode skips/ignore Error HandlingNeeds Feedback2020-06-29


Updated by Jonathan Starck over 1 year ago

  • Category set to Link Handling, Site Handling & 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 1 year ago

  • Related to Bug #91722: Maintenance Mode skips/ignore Error Handling added

Updated by Oliver Bartsch about 2 months 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 2 months 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 2 months 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.

Also available in: Atom PDF