You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrading from the bugsnag 2.x to 6.x and trying to get an express app erroring correctly. Right now when it errors via an uncaught expectation (I added sdfsa.fafsadf; so it threw an undefined error, to a route), it throws a 200 with "Internal server error"
Thanks for the report. Since we also support Connect using the same middleware, this needs to be res.statusCode = 500 rather than res.status(). I've scheduled a fix.
The wrong property was being used in attempt to set the HTTP status code. This fixes it for Express
and Connect (connect doesn't have the method res.status()).
Fixes#510.
The wrong property was being used in attempt to set the HTTP status code. This fixes it for Express
and Connect (connect doesn't have the method res.status()).
Fixes#510.
Upgrading from the bugsnag 2.x to 6.x and trying to get an express app erroring correctly. Right now when it errors via an uncaught expectation (I added
sdfsa.fafsadf;
so it threw an undefined error, to a route), it throws a 200 with "Internal server error"Looking at node js, res.status is how a status code is set, but it's a function https://expressjs.com/en/api.html#res.end
in the bugsnag express code, it's
switching it to res.status(500) correctly sends a 500 status code
The text was updated successfully, but these errors were encountered: