#107684Modify how $GLOBALS['TYPO3_CONF_VARS']['FE']['pageUnavailable_force'] works
Description
When activating $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘pageUnavailable_force’] it shows that the page is unavailable, which is OK.
The HTTP code that is thrown is a 503. However, if in a Site Configuration an Error Handler is configured to Handle a 503 to show a page (or file or what is configured as “callback”), the configured element will not be shown because the sub-request still returns a 503, and, as a result, the Error Handler configuration is ignored since the returned response is a “Server Error”.
Does this makes sense?
Maybe, if a Error Handler is configured when $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘pageUnavailable_force’] the content of that Error Handler should be shown to be able to easily configure a “Maintenance Mode” for the Frontend if needed.
So, as a summary, maybe developers and/or site admins may expect that when $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘pageUnavailable_force’] and a Error Handler is configured for that case, the content of that Handler is shown.
Regards.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.