</>DevTools

HTTP Status Code Reference

Quick reference for all standard HTTP status codes.

1xxInformational

100

Continue

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

101

Switching Protocols

The server is switching protocols as requested by the client (e.g., WebSocket).

102

Processing

WebDAV: the server has received and is processing the request.

2xxSuccess

200

OK

Standard response for successful HTTP requests.

201

Created

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

202

Accepted

The request has been accepted for processing but not yet completed.

204

No Content

The server successfully processed the request, returning no content.

206

Partial Content

The server is delivering only part of the resource (range requests).

3xxRedirection

301

Moved Permanently

The resource has been permanently moved to a new URL.

302

Found

The resource is temporarily located at a different URL.

304

Not Modified

The cached version is still valid; no body is returned.

307

Temporary Redirect

The request should be repeated with the same method at the new URL.

308

Permanent Redirect

The request and future requests should use the new URL.

4xxClient Error

400

Bad Request

The server cannot process the request due to client error.

401

Unauthorized

Authentication is required and has failed or not been provided.

403

Forbidden

The server understood the request but refuses to authorize it.

404

Not Found

The requested resource could not be found on the server.

405

Method Not Allowed

The HTTP method used is not allowed for this resource.

408

Request Timeout

The server timed out waiting for the request.

409

Conflict

The request conflicts with the current state of the resource.

410

Gone

The resource is no longer available and will not be available again.

413

Payload Too Large

The request entity is larger than the server is willing to process.

415

Unsupported Media Type

The request entity has a media type the server cannot process.

422

Unprocessable Entity

The request was well-formed but could not be followed due to semantic errors.

429

Too Many Requests

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

5xxServer Error

500

Internal Server Error

A generic error occurred on the server.

501

Not Implemented

The server does not support the functionality required to fulfill the request.

502

Bad Gateway

The server, while acting as a gateway, received an invalid response from upstream.

503

Service Unavailable

The server is not ready to handle the request (overloaded or down for maintenance).

504

Gateway Timeout

The server, acting as a gateway, did not receive a timely response from upstream.