HTTP Status Codes

Complete reference of HTTP response status codes.

Showing 62 status codes

100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The server is switching protocols as requested by the client.

102

Processing

The server has received and is processing the request, but no response is available yet.

103

Early Hints

Used to return some response headers before final HTTP message.

200

OK

The request has succeeded. The meaning depends on the HTTP method used.

201

Created

The request has succeeded and a new resource has been created.

202

Accepted

The request has been received but not yet acted upon.

203

Non-Authoritative Information

The returned metadata is from a local or third-party copy.

204

No Content

The server successfully processed the request but returns no content.

205

Reset Content

The server processed the request and asks the client to reset the document view.

206

Partial Content

The server is delivering only part of the resource due to a range header.

207

Multi-Status

Conveys information about multiple resources in situations where multiple status codes might be appropriate.

208

Already Reported

Used inside a DAV: propstat response element to avoid enumerating internal members repeatedly.

226

IM Used

The server has fulfilled a GET request for the resource with instance manipulations applied.

300

Multiple Choices

The request has multiple possible responses. The user should choose one.

301

Moved Permanently

The URL of the requested resource has been changed permanently.

302

Found

The URI of the requested resource has been changed temporarily.

303

See Other

The server sent this response to direct the client to get the resource at another URI with a GET request.

304

Not Modified

Indicates that the resource has not been modified since the version specified in the request headers.

305

Use Proxy

The requested resource must be accessed through a proxy. Deprecated.

307

Temporary Redirect

The server sends this response to direct the client to get the resource at another URI with the same method.

308

Permanent Redirect

The resource is now permanently located at another URI, specified in the Location header.

400

Bad Request

The server cannot process the request due to client error (malformed syntax, invalid request).

401

Unauthorized

Authentication is required and has failed or has not been provided.

402

Payment Required

Reserved for future use. Originally intended for digital payment systems.

403

Forbidden

The client does not have access rights to the content.

404

Not Found

The server cannot find the requested resource.

405

Method Not Allowed

The request method is known by the server but not supported by the target resource.

406

Not Acceptable

The server cannot produce a response matching the list of acceptable values.

407

Proxy Authentication Required

The client must first authenticate itself with the proxy.

408

Request Timeout

The server timed out waiting for the request.

409

Conflict

The request conflicts with the current state of the server.

410

Gone

The content has been permanently deleted from the server.

411

Length Required

The server requires the Content-Length header field in the request.

412

Precondition Failed

The server does not meet one of the preconditions specified in the request headers.

413

Payload Too Large

The request entity is larger than limits defined by the server.

414

URI Too Long

The URI requested by the client is longer than the server is willing to interpret.

415

Unsupported Media Type

The media format of the requested data is not supported by the server.

416

Range Not Satisfiable

The range specified in the Range header cannot be fulfilled.

417

Expectation Failed

The expectation indicated in the Expect header cannot be met by the server.

418

I'm a Teapot

The server refuses to brew coffee because it is a teapot. (April Fools joke from 1998)

421

Misdirected Request

The request was directed at a server that is not able to produce a response.

422

Unprocessable Entity

The request was well-formed but contains semantic errors.

423

Locked

The resource that is being accessed is locked.

424

Failed Dependency

The request failed due to failure of a previous request.

425

Too Early

The server is unwilling to risk processing a request that might be replayed.

426

Upgrade Required

The server refuses to perform the request using the current protocol.

428

Precondition Required

The origin server requires the request to be conditional.

429

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

431

Request Header Fields Too Large

The server refuses to process the request because its headers are too large.

451

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand.

500

Internal Server Error

The server has encountered a situation it does not know how to handle.

501

Not Implemented

The request method is not supported by the server and cannot be handled.

502

Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response.

503

Service Unavailable

The server is not ready to handle the request. Common causes are maintenance or overload.

504

Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response.

505

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.

506

Variant Also Negotiates

The server has an internal configuration error.

507

Insufficient Storage

The server is unable to store the representation needed to complete the request.

508

Loop Detected

The server detected an infinite loop while processing the request.

510

Not Extended

Further extensions to the request are required for the server to fulfill it.

511

Network Authentication Required

The client needs to authenticate to gain network access.

Quick Reference

1xx
Informational
2xx
Success
3xx
Redirection
4xx
Client Error
5xx
Server Error

About HTTP Status Codes

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped into five classes: informational, successful, redirects, client errors, and server errors.

Common Status Codes