What is the correct http status code when URI parameter is wrong

Question

Given i have a HTTP-Interface, and for example

POST /user

expects some specific JSON to be posted (for example {"username": "keppla"}), or

GET /search

expects a parameter like /search?term=whatisearch

When the client does not send the expected data, what would be a correct error code?

just send a 200 with a json error object, it is more customisable in most cases that way anyway — davin
– davin, Commented Apr 18, 2011 at 9:43
hmmm, i could have sworn i wrote 400, and its too late to edit... — davin
– davin, Commented Apr 18, 2011 at 12:23

isobar · Accepted Answer · 2011-04-18 09:44:32Z

6

400-499 is range for incomplete client requests. Looks like 400 is the right error code for your use case.

400 - Bad Request, The server could not understand the request, probably due to a syntax error.

answered Apr 18, 2011 at 9:44

isobar

1,1758 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

keppla Over a year ago

i felt, the 'probably due to syntax error' would be kind of misleading (the requests are syntactically correct).

isobar Over a year ago

There is also 417, Expectation failed, Value in the Expect request header could not be met

keppla Over a year ago

but there's no request expectaion. As i understand 417, it is to answer to requests with 'expect' headers. 400 seems to be more apropriate

isobar Over a year ago

hmm yeah right, 417 is about the server not able to meet the expectation w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.18 400 seems appropriate.

andho Over a year ago

400 seems appropriate. Syntax error as in your application is expecting /search?term=whatever but unexpectadly request ended with /search or requested contains unexpected /search?term=' inject sql'

Darrel Miller · Accepted Answer · 2011-04-18 12:28:40Z

4

422 is a possibility, but it is not commonly used, as it is not widely known that it is permissible to use WEBDAV status codes even when you are not doing WEBDAV.

422 - The request was well-formed but was unable to be followed due to semantic errors

For the second scenario, you could argue that a 404 is more appropriate as it is the URI that is not correctly formed, rather than the request body.

answered Apr 18, 2011 at 12:28

Darrel Miller

143k32 gold badges202 silver badges246 bronze badges

Collectives™ on Stack Overflow

What is the correct http status code when URI parameter is wrong

2 Answers 2

5 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

5 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related