Layer 7 Video on REST API Error Handling
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts
Tuesday, 19 February 2013
Friday, 5 October 2012
REST Web Service API HTTP Response Status Codes
What HTTP status codes should your REST web service API be returning to clients? Does it matter? Before we launch into this topic, a quick recap of some interesting HTTP status codes:
200 - "OK" All is well
204 - "No Content" Nothing returned, but all is still well
400 - "Bad Request" There is problem on the client's side
500 - "Internal Server Error" There is a problem on the server side
301 - "Moved Permanently" The resource has moved
303 - "See Other Server" Returns a URI to another resource
404 - "Not Found" Server has no clue what the client is asking for
409 - "Conflict" Client has tried to perform an operation that would leave one or more resources in an inconsistent state
401 - "Unauthorized" Client attempted access to a resource without providing the necessary authentication credentials
403 - "Forbidden" Client is not authorised to access a resource
200 - "OK" All is well
204 - "No Content" Nothing returned, but all is still well
400 - "Bad Request" There is problem on the client's side
500 - "Internal Server Error" There is a problem on the server side
301 - "Moved Permanently" The resource has moved
303 - "See Other Server" Returns a URI to another resource
404 - "Not Found" Server has no clue what the client is asking for
409 - "Conflict" Client has tried to perform an operation that would leave one or more resources in an inconsistent state
401 - "Unauthorized" Client attempted access to a resource without providing the necessary authentication credentials
403 - "Forbidden" Client is not authorised to access a resource