StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCatch express bodyParser error
primarykey
Id
15819337
data
AcceptedAnswerId
15819808
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-04T18:50:17.583
FavoriteCount
3
LastActivityDate
2018-06-15T15:23:28.120
LastEditDate
2013-04-04T19:06:18.623
LastEditorUserId
458093
OwnerUserId
458093
ParentId
0
PostTypeId
1
Score
32
ViewCount
15675
LastEditorDisplayName
text
Body
I want to catch the error from the bodyParser() middleware when I send a json object and it is invalid because I want to send a custom response instead of a generic 400 error. This is what I have and it works: <pre><code>app.use (express.bodyParser ()); app.use (function (error, req, res, next){ //Catch bodyParser error if (error.message === "invalid json"){ sendError (res, myCustomErrorMessage); }else{ next (); } }); </code></pre> But this seems to me a very ugly approach because I'm comparing the error message which could change in future express versions. There's any other way to catch bodyParser() errors? EDIT: This is the error when the request body has an invalid json: <pre><code>{ stack: 'Error: invalid json\n at Object.exports.error (<path>/node_modules/express/node_modules/connect/lib/utils.js:55:13)\n at IncomingMessage.<anonymous> (<path>/node_modules/express/node_modules/connect/lib/middleware/json.js:74:71)\n at IncomingMessage.EventEmitter.emit (events.js:92:17)\n at _stream_readable.js:872:14\n at process._tickDomainCallback (node.js:459:13)', arguments: undefined, type: undefined, message: 'invalid json', status: 400 } </code></pre> Pretty printed stack: <pre><code>Error: invalid json at Object.exports.error (<path>/node_modules/express/node_modules/connect/lib/utils.js:55:13) at IncomingMessage.<anonymous> (<path>/node_modules/express/node_modules/connect/lib/middleware/json.js:74:71) at IncomingMessage.EventEmitter.emit (events.js:92:17) at _stream_readable.js:872:14 at process._tickDomainCallback (node.js:459:13) </code></pre>
Tags
<javascript><node.js><express>
Title
Catch express bodyParser error
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USGabriel Llamas
UserOwnerUserId
1. USGabriel Llamas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCatch express bodyParser error
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POCatch express bodyParser error
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.