Issue Bug Closed

#72034200 HTTP status is returned when handling runtime errors in Production context

Gabe Blair 12/02/15, 23:41 updated 03/20/16, 21:32

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.