Códigos de estado HTTP

100 Continue

The server got the request headers; the client should send the body.

101 Switching Protocols

The server is switching protocols as requested, e.g. upgrading to WebSocket.

102 Processing

WebDAV: the request is received and being processed, no response yet.

103 Early Hints

Lets the browser preload resources (Link headers) before the final response.

200 OK

The request succeeded. The body contains the result.

201 Created

A new resource was created. Usually returned for POST, with a Location header.

202 Accepted

The request was accepted for processing, but is not finished yet (async jobs).

203 Non-Authoritative Information

The response was modified by a proxy from the origin’s 200 response.

204 No Content

Success with no body. Common for DELETE or PUT.

205 Reset Content

Success; the client should reset the form or view that sent the request.

206 Partial Content

Only part of the resource is returned, in response to a Range header (video, resumable downloads).

207 Multi-Status

WebDAV: multiple status codes for multiple operations in one body.

208 Already Reported

WebDAV: members already listed earlier in the response.

226 IM Used

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

300 Multiple Choices

There are several possible responses; the client should pick one.

301 Moved Permanently

The resource has a new permanent URL. Search engines transfer ranking. Method may change to GET.

302 Found

Temporary redirect. Browsers usually switch to GET.

303 See Other

Redirect to another URL with GET — typical after a form POST.

304 Not Modified

The cached version is still valid (conditional GET with If-None-Match / If-Modified-Since).

307 Temporary Redirect

Temporary redirect that keeps the original method and body.

308 Permanent Redirect

Permanent redirect that keeps the original method and body.

400 Bad Request

The request is malformed — invalid syntax, bad JSON or missing parameters.

401 Unauthorized

Authentication is missing or invalid. Send credentials (WWW-Authenticate header says how).

402 Payment Required

Reserved; sometimes used for paywalls or exhausted quotas.

403 Forbidden

The server knows who you are but you are not allowed to access this.

404 Not Found

No resource exists at this URL.

405 Method Not Allowed

The HTTP method is not supported for this URL. The Allow header lists valid ones.

406 Not Acceptable

The server cannot produce a format matching the Accept headers.

407 Proxy Authentication Required

Like 401, but the proxy requires authentication.

408 Request Timeout

The client took too long to send the request.

409 Conflict

The request conflicts with the current state, e.g. an edit conflict or duplicate.

410 Gone

The resource was deleted permanently and will not come back.

411 Length Required

The server requires a Content-Length header.

412 Precondition Failed

A condition like If-Match failed — often used for optimistic locking.

413 Content Too Large

The request body is larger than the server allows (upload limits).

414 URI Too Long

The URL is longer than the server will handle.

415 Unsupported Media Type

The body format (Content-Type) is not supported.

416 Range Not Satisfiable

The requested Range is outside the resource’s size.

417 Expectation Failed

The Expect header could not be met.

418 I'm a teapot

An April Fools’ joke from RFC 2324. The server refuses to brew coffee.

421 Misdirected Request

The request went to a server that cannot answer for this host.

422 Unprocessable Content

The syntax is fine but the data fails validation. Popular for form/API validation errors.

423 Locked

WebDAV: the resource is locked.

424 Failed Dependency

WebDAV: failed because a previous request failed.

425 Too Early

The server will not process a request that might be replayed (TLS early data).

426 Upgrade Required

The client must switch to another protocol, given in the Upgrade header.

428 Precondition Required

The server requires a conditional request (e.g. If-Match) to avoid lost updates.

429 Too Many Requests

Rate limit hit. Check the Retry-After header.

431 Request Header Fields Too Large

The headers (often cookies) are too large.

451 Unavailable For Legal Reasons

Blocked for legal reasons, such as censorship or a court order.

500 Internal Server Error

A generic server-side error — something crashed or threw.

501 Not Implemented

The server does not support the functionality needed.

502 Bad Gateway

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

503 Service Unavailable

The server is overloaded or down for maintenance. Often temporary; may include Retry-After.

504 Gateway Timeout

A proxy or gateway did not get a response from upstream in time.

505 HTTP Version Not Supported

The HTTP version in the request is not supported.

506 Variant Also Negotiates

Server configuration error in content negotiation.

507 Insufficient Storage

WebDAV: the server cannot store the representation.

508 Loop Detected

WebDAV: an infinite loop was detected.

510 Not Extended

Further extensions are required for the request.

511 Network Authentication Required

You must log in to the network, e.g. a Wi-Fi captive portal.