Status Codes

200 OK

The request is successful. The response header or message body will be returned with the response.

201 Created

When the POST or PUT operation is successful, status code 201 (Created) is returned with the URI in the Location field of the new resource in the message header.

202 Accepted

The request has been accepted for processing, but the process has not been completed. A resource has been created according to the request and the request URI is returned with the Location field in the message header.

204 No Content

The server has processed the request but does not return any content.

206 Partial Content

The server has processed certain GET requests.

302 Found

The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client should continue to use the Request-URI for future requests.

303 See Other

The response to the request can be found under a different URI and should be retrieved using the GET method on that resource.

304 Not Modified

The document has not been modified as expected. The client has a cached document and has sent a conditional request. (In most cases, the If-Modified-Since header is provided, indicating that the client uses only documents updated after a specified date.) The server uses this code to notify the client that the cached document is available.

400 Bad Request

1. The request cannot be understood by the server due to malformed syntax. The client should not send the request repeatedly without modifications.

2. Request parameters are incorrect.

401 Unauthorized

Used only in the HTTPS (BASIC authentication, DIGET authentication) authentication scenarios. If there are other authentication mechanisms, status code 403 is returned after authentication failure. The response must include the header WWW-Authenticate for user information query.

403 Forbidden

If the request method is not HEAD, the server must describe the reason for the refusal in the message body. If the cause cannot be disclosed, 404 Not Found is returned.

404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The status code 410 should be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. The status code 404 is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

405 Method Not Allowed

You are not allowed to use the method specified in the request. The response must include an Allow header containing a list of valid methods for the requested resource. Since the PUT and DELETE methods will write resources on the server, the preceding methods are not supported or allowed by default by most servers. The server will return 405 (Method Not Allowed) for this type of requests.

409 Conflict

The request cannot be completed due to a conflict with the current state of the resource. Conflicts are most likely to occur in response to a PUT request.

414 Request-URI Too Long

The URL can contain a maximum of 2083 characters.

429 Too Many Requests

The number of requests sent to the server in a given period of time has exceeded the threshold.

500 Internal Server Error

An unexpected error occurs on the server. As a result, the server cannot process the request.

502 Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

503 Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance of the server.