A List of Common HTTP Status Codes

200 All is good; response will include applicable resource information, as well.

201 Resource created; will include the Location header specifying a URI to the newly created resource.

202 Same as 200, but used for async; in other words, all is good, but we need to poll the service to find out when completed.

301 The resource was moved; should include URI to new location.

400 Bad request; caller should reformat the request.

401 Unauthorized; should respond with an authentication challenge, to let the caller resubmit with appropriate credentials.

403 Access denied; user successfully authenticated, but is not allowed to access the requested resource.

404 Resource not found, or, caller not allowed to access the resource and we don’t want to reveal the reason.

409 Conflict; used as a response to a PUT request when another caller has dirtied the resource.

500 Server error; something bad happened, and server might include some indication of the underlying problem.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s