Project

General

Profile

Actions
Copy link

Bug #72034

closed

200 HTTP status is returned when handling runtime errors in Production context

Added by Gabe Blair over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
Candidate for patchlevel
Start date:
2015-12-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

This seems wrong. The default exception handler for Production contexts should throw a `500` when there's a problem. Instead, we see something like, `Oops, an error occurred! Code: 20151202221702d83e4ffe` with a `200` response code. I know our clients don't want to see stuff like that show up on web searches, indexed by solr, etc., or getting cached/returned by proxies, CDNs, etc. We also use the status code as part of a smoke testing suite on some of our projects post-deployment, so that test is rendered useless.

Actions
Copy link

Also available in: Atom PDF