Status Codes

Table 1 describes status codes.

Table 1 Status codes

Status Code

Message

Description

100

Continue

The client should continue with its request.

This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server.

101

Switching Protocols

The protocol should be switched. The protocol can only be switched to a more advanced protocol.

For example, the current HTTP protocol is switched to a later version.

200

OK

Request succeeded.

201

Created

The request for creating a resource or task has been fulfilled.

202

Accepted

The request has been accepted, but the processing has not been completed.

203

Non-Authoritative Information

Unauthorized information. The request is successful.

204

NoContent

The server has successfully processed the request, but has not returned any content.

The status code is returned in response to an HTTP OPTIONS request.

205

Reset Content

The server has fulfilled the request, but the requester is required to reset the content.

206

Partial Content

The server has processed certain GET requests.

300

Multiple Choices

There are multiple options for the location of the requested resource. The response contains a list of resource characteristics and addresses from which the user or user agent (such as a browser) can choose the most appropriate one.

301

Moved Permanently

The requested resource has been assigned a new permanent URI, and the new URI is contained in the response.

302

Found

The requested resource was temporarily moved.

303

See Other

The response to the request can be found under a different URI and should be retrieved using a GET or POST method.

304

Not Modified

The requested resource has not been modified. In such a case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.

305

Use Proxy

The requested resource must be accessed through a proxy.

306

Unused

The HTTP status code is no longer used.

400

BadRequest

Invalid request.

The client should not repeat the request without modifications.

401

Unauthorized

The status code is returned after the client provides the authentication information, indicating that the authentication information is incorrect or invalid.

402

Payment Required

This status code is reserved for future use.

403

Forbidden

The server understood the request, but is refusing to fulfill it.

The client should not repeat the request without modifications.

404

NotFound

The requested resource cannot be found.

The client should not repeat the request without modifications.

405

MethodNotAllowed

The method specified in the request is not supported for the requested resource.

The client should not repeat the request without modifications.

406

Not Acceptable

The server cannot fulfill the request according to the content characteristics of the request.

407

Proxy Authentication Required

This status code is similar to 401, but indicates that the client must first authenticate itself with the proxy.

408

Request Time-out

The server timed out waiting for the request.

The client may repeat the request without modifications at any later time.

409

Conflict

The request could not be processed due to a conflict.

This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.

410

Gone

The requested resource is no longer available.

The requested resource has been deleted permanently.

411

Length Required

The server refuses to process the request without a defined Content-Length.

412

Precondition Failed

The server does not meet one of the preconditions that the requester puts on the request.

413

Request Entity Too Large

The request is larger than that a server is able to process. The server may close the connection to prevent the client from continuing the request. If the server temporarily cannot process the request, the response will contain a Retry-After header field.

414

Request-URI Too Large

The URI provided was too long for the server to process.

415

Unsupported Media Type

The server is unable to process the media format in the request.

416

Requested range not satisfied

The requested range is invalid.

417

Expectation Failed

The server fails to meet the requirements of the Expect request-header field.

422

UnprocessableEntity

The request is well-formed but is unable to be processed due to semantic errors.

429

TooManyRequests

The client has sent more requests than its rate limit is allowed within a given amount of time, or the server has received more requests than it is able to process within a given amount of time. In this case, it is advisable for the client to re-initiate requests after the time specified in the Retry-After header of the response expires.

500

InternalServerError

The server is able to receive the request but it could not understand the request.

501

Not Implemented

The server does not support the requested function.

502

Bad Gateway

The server acting as a gateway or proxy receives an invalid response from a remote server.

503

ServiceUnavailable

The requested service is invalid.

The client should not repeat the request without modifications.

504

ServerTimeout

The request cannot be fulfilled within a given time. The response will reach the client only if the request carries a timeout parameter.

505

HTTP Version not supported

The server does not support the HTTP protocol version used in the request.