Bug #72034
closed
200 HTTP status is returned when handling runtime errors in Production context
0%
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.
Updated by Frank Nägler over 8 years ago
- Status changed from New to Needs Feedback
- Target version changed from 7.6.1 to Candidate for patchlevel
- Complexity deleted (
easy) - Is Regression changed from Yes to No
Do you use custom ProductionExceptionHandler?
Can you give some more information hwo to reproduce it? Which settings do you use in install tool for error handling
Updated by Riccardo De Contardi about 8 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
You could also join the #typo3-cms channel in Slack if you still need support.
Thank you