OpenReplay Logo
12k
12k

HTTP status codes

Every HTTP status code (1xx–5xx) with its name and meaning — searchable, deep-linkable and developer-friendly. A quick reference from OpenReplay.

Static reference — nothing is sent anywhere

Click a code to copy its anchor link

1xx — Informational

The request was received and the process is continuing.

100 Continue

The client should continue with its request; the initial part was received.

101 Switching Protocols

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

102 Processing

The server has accepted the request but has not yet completed it (WebDAV).

103 Early Hints

Returns preliminary headers (e.g. Link) so the client can begin preloading.

2xx — Success

The request was successfully received, understood and accepted.

200 OK

Standard success response; the meaning depends on the HTTP method used.

201 Created

The request succeeded and a new resource was created.

202 Accepted

The request was accepted for processing but is not yet complete.

203 Non-Authoritative Information

Returned metadata came from a copy, not the origin server.

204 No Content

The request succeeded but there is no body to return.

205 Reset Content

Success; the client should reset the document view that sent the request.

206 Partial Content

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

207 Multi-Status

Conveys multiple independent status codes for a WebDAV request.

208 Already Reported

Members of a WebDAV binding were already enumerated and are not repeated.

226 IM Used

The response is the result of instance manipulations applied to the resource.

3xx — Redirection

Further action is needed to complete the request.

300 Multiple Choices

The request has more than one possible response; the client should choose.

301 Moved Permanently

The resource moved permanently to a new URL; update links to it.

302 Found

The resource is temporarily at a different URL; keep using the original.

303 See Other

Fetch the resource at another URI with a GET request.

304 Not Modified

The cached version is still valid; the client can reuse it.

307 Temporary Redirect

Like 302 but the method and body must not change on the redirect.

308 Permanent Redirect

Like 301 but the method and body must not change on the redirect.

4xx — Client error

The request contains bad syntax or cannot be fulfilled.

400 Bad Request

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

401 Unauthorized

Authentication is required and has failed or not been provided.

402 Payment Required

Reserved for future use; sometimes used by APIs for rate or quota limits.

403 Forbidden

The server understood the request but refuses to authorize it.

404 Not Found

The server cannot find the requested resource.

405 Method Not Allowed

The HTTP method is not supported for the target resource.

406 Not Acceptable

No representation matches the request’s Accept headers.

407 Proxy Authentication Required

The client must authenticate with a proxy first.

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 permanently gone and no forwarding address is known.

411 Length Required

The request must include a Content-Length header.

412 Precondition Failed

A precondition in the request headers evaluated to false.

413 Payload Too Large

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

414 URI Too Long

The requested URI is longer than the server will interpret.

415 Unsupported Media Type

The request’s media type is not supported by the resource.

416 Range Not Satisfiable

The requested Range cannot be served.

417 Expectation Failed

The Expect request header could not be met.

418 I'm a teapot

An April Fools’ joke code (RFC 2324); the server refuses to brew coffee.

421 Misdirected Request

The request was directed at a server unable to produce a response.

422 Unprocessable Content

The request was well-formed but had semantic errors (WebDAV / APIs).

423 Locked

The resource being accessed is locked (WebDAV).

424 Failed Dependency

The request failed because a previous request it depended on failed.

425 Too Early

The server is unwilling to risk processing a possibly replayed request.

426 Upgrade Required

The client should switch to a different protocol given in the Upgrade header.

428 Precondition Required

The origin server requires the request to be conditional.

429 Too Many Requests

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

431 Request Header Fields Too Large

The headers are too large for the server to process.

451 Unavailable For Legal Reasons

The resource is unavailable due to legal demands.

5xx — Server error

The server failed to fulfil a valid request.

500 Internal Server Error

A generic error; the server hit an unexpected condition.

501 Not Implemented

The server does not support the functionality to fulfil the request.

502 Bad Gateway

A gateway or proxy received an invalid response from the upstream server.

503 Service Unavailable

The server is temporarily overloaded or down for maintenance.

504 Gateway Timeout

A gateway or proxy did not get a timely response from the upstream server.

505 HTTP Version Not Supported

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

506 Variant Also Negotiates

A content-negotiation configuration error on the server.

507 Insufficient Storage

The server cannot store the representation needed to complete the request (WebDAV).

508 Loop Detected

The server detected an infinite loop while processing the request (WebDAV).

510 Not Extended

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

511 Network Authentication Required

The client must authenticate to gain network access (e.g. captive portals).

About this tool

HTTP status codes are the three-digit numbers a server returns with every response, telling the client what happened. They're grouped into five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client errors and 5xx server errors.

This page lists the standard codes in each class with a concise explanation of what each means and when you will see it. Search by number or name to jump to one, and use the per-code anchors (for example #404) to deep-link a specific status — handy when debugging an API response or a failing request.

A static reference rendered entirely in your browser — nothing is sent anywhere.

Frequently asked questions

What's the difference between 401 and 403?

401 Unauthorized means you're not authenticated — log in or send valid credentials and retry. 403 Forbidden means you are authenticated but not allowed to access the resource; retrying with the same identity won't help.

When should I use 301 vs 302?

301 Moved Permanently tells clients and search engines the resource has a new permanent URL (they should update links and caches). 302 Found (and 307) are temporary — keep using the original URL.

What does a 5xx code mean for me?

5xx codes indicate the server failed to handle a valid request — the problem is server-side, not your request. Common ones are 500 (generic error), 502 (bad upstream response) and 503 (temporarily unavailable).