Project

General

Profile

Actions

Bug #93045

closed

500 vs 503 error handling is not consistent

Added by Benjamin Franzke almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2020-12-10
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

For 5xx status code we have two different cases right now * configuration errors, which need to respond with 500 * maintenance mode, which is a 503 response

In 10.4.10 always 500 is returned, in master and 10.4 branch currently 503. This should be streamlined.

Also the 500 or 503 site error handler in maintenace middleware isn't invoked as the maintenace mode middleware is executed before the site resolver middleware.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #93032: Change status code from 500 to 503Closed2020-12-09

Actions
Actions

Also available in: Atom PDF