TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #93032
Issue Task Closed

#93032Change status code from 500 to 503

TYPO3 GmbH TYPO3com 12/09/20, 02:42 updated 12/22/20, 11:02

Open in Forge Comment in Forge

Description

Page Unavailable is 503, not 500. If TYPO3 is in maintenance mode and you’ve configured an Error Handler in your Site Configuration for 503, it doesn’t actually get used.

This issue was automatically created from https://github.com/TYPO3/TYPO3.CMS/pull/286

Reviews 5

  • 10.4 67306[BUGFIX] Streamline frontend 5xx error handling Related to this issue Merged Christian Kuhn CR +2 V +2 → main Normal +176 −32 01/06/21, 13:36
  • main 67080[BUGFIX] Streamline frontend 5xx error handling Related to this issue Merged Benjamin Franzke CR +2 V +2 → 10.4 Normal +172 −31 01/06/21, 11:48
  • main 67074[TASK] Change page unavailable status code from 500 to 503 Resolves this issue Merged TYPO3com CR +2 V +2 → 10.4 Easy +5 −5 12/10/20, 08:43
  • 10.4 67055[TASK] Change page unavailable status code from 500 to 503 Resolves this issue Merged Benni Mack CR +2 V +2 → main Easy +5 −5 12/10/20, 08:36
  • 9.5 67078[TASK] Change page unavailable status code from 500 to 503 Resolves this issue Abandoned Benjamin Franzke CR 0 V 0 → main, 10.4 Easy +11 −4 12/10/20, 05:47

Related issues 1

  • Bug #93045500 vs 503 error handling is not consistent Related to Closed Frontend v11 Benjamin Franzke 12/10/20, 07:48
Author
TYPO3 GmbH TYPO3com
Priority
Should have
TYPO3 version
10
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback