This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

RESTful web services and status code philosophy

 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64632
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64632
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Peer!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic