| Author |
RESTful web services and status code philosophy
|
Bear Bibeault
Author and ninkuma
Marshal
Joined: Jan 10, 2002
Posts: 56220
|
|
OK, for a GET specifying a record (or some such) that doesn't exist, the response has status code 404 (not found). That's easy.
But what about a PUT that fails because the user gave bad input?
404 doesn't seem to cut it. And there doesn't seem to be any other pre-defined status codes that don't already have some heavy HTTP semantics associated with them.
What's the appropriate return code?
Overall, what's the philosophy to choosing status codes for a RESTful service?
|
[Smart Questions] [JSP FAQ] [Books by Bear] [Bear's FrontMan] [About Bear]
|
 |
Peer Reynders
Bartender
Joined: Aug 19, 2005
Posts: 2906
|
|
Originally posted by Bear Bibeault:
But what about a PUT that fails because the user gave bad input?
400 "Bad Request"
It's commonly used when the client submits a representation along with a put or POST request, and the representation is in the right format, but doesn't make any sense.
Overall, what's the philosophy to choosing status codes for a RESTful service?
"Appendix B: The HTTP Response Code Top 42" from RESTful Web Services
|
"Don't succumb to the false authority of a tool or model. There is no substitute for thinking."
Andy Hunt, Pragmatic Thinking & Learning: Refactor Your Wetware p.41
|
|
Bear Bibeault
Author and ninkuma
Marshal
Joined: Jan 10, 2002
Posts: 56220
|
|
|
Thanks Peer!
|
|
 |
|
|
subject: RESTful web services and status code philosophy
|
|
|
0
