Send 400 response for malformed JSON in input #156

Closed
strk opened this Issue Feb 25, 2014 · 1 comment

2 participants

@strk

Right now 500 http status is raised, handled by express when middleware calls "next" with an error.

@strk strk added the bug label Feb 25, 2014
@strk strk referenced this issue in CartoDB/Windshaft-cartodb Feb 25, 2014
Closed

wrong json format on named map creations raises 500 #162

@strk

The only way to respond with a meaningful error would be to control the call to the "body parser" near to each endpoint, rather than once very early in the routing table.

@rochoa rochoa was assigned by javisantana Apr 3, 2014
@rochoa rochoa closed this Aug 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment