›_ HTTP STATUS CODES

Every HTTP status code on its own page. Each entry covers what the code means, when servers should return it, common causes (for errors), how to fix them, a real curl example, related codes, and a small FAQ. 49 codes documented. Search by number or keyword.

Source of truth: RFC 9110 + extension RFCs One-page version: cheat sheet Curl reference: cheat sheet

1xx Informational

Request received and processing continues

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, typically upgrading from HTTP/1.1 to WebSocket.
103
Early Hints
The server hints at resources the client can preload while the final response is still being prepared.

2xx Success

Request was successfully received, understood, and accepted

200
OK
The request succeeded. The response body contains whatever the request was for.
201
Created
The request succeeded and a new resource was created as a result.
202
Accepted
The request has been accepted for processing but has not yet completed.
204
No Content
The request succeeded and there is intentionally no response body.
206
Partial Content
The server is delivering only part of the resource, in response to a Range request from the client.
207
Multi-Status
The response contains a result for multiple sub-operations, each with its own status.

3xx Redirection

Further action must be taken to complete the request

301
Moved Permanently
The resource has permanently moved to a new URL given in the Location header.
302
Found
The resource is temporarily at a different URL. Use the new URL for this request only.
303
See Other
The response to your request can be found at a different URL, and you should fetch it with GET.
304
Not Modified
The cached version of the resource is still valid; no body is sent.
307
Temporary Redirect
The resource is temporarily at a different URL. Use the same HTTP method to access it.
308
Permanent Redirect
The resource has permanently moved and the same HTTP method must be used at the new URL.

4xx Client Error

The request contains bad syntax or cannot be fulfilled

400
Bad Request
The server cannot process the request because the client sent something invalid.
401
Unauthorized
The request requires authentication that was not provided or was invalid.
402
Payment Required
Reserved for future use; in practice, used by some APIs to signal the caller has run out of credits.
403
Forbidden
The server understood the request and knows who you are, 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 this resource.
406
Not Acceptable
The server cannot produce a response matching the client's Accept headers.
408
Request Timeout
The server gave up waiting for the client to finish sending the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is permanently gone and will not return.
411
Length Required
The request lacks a Content-Length header that the server requires.
412
Precondition Failed
A precondition header on the request did not match the server's state.
413
Content Too Large
The request body exceeds the server's size limit.
414
URI Too Long
The URL is longer than the server is willing to interpret.
415
Unsupported Media Type
The server cannot parse the Content-Type of the request body.
416
Range Not Satisfiable
The requested byte range is outside the resource's actual size.
418
I'm a Teapot
The server is a teapot and refuses to brew coffee.
422
Unprocessable Content
The request is well-formed but contains semantically invalid data.
423
Locked
The resource is locked and cannot be modified right now.
425
Too Early
The server is unwilling to risk processing a request that might be replayed.
426
Upgrade Required
The client must upgrade to a different protocol to continue.
428
Precondition Required
The server requires the request to be conditional.
429
Too Many Requests
The client has sent too many requests in too short a time and is being rate-limited.
431
Request Header Fields Too Large
The request headers, in total or individually, exceed the server's limit.
451
Unavailable For Legal Reasons
The resource is blocked due to a legal demand.

5xx Server Error

The server failed to fulfill an apparently valid request

500
Internal Server Error
The server hit an unhandled error while processing the request.
501
Not Implemented
The server does not support the request method or feature.
502
Bad Gateway
A gateway or proxy got an invalid response from an upstream server.
503
Service Unavailable
The server is temporarily unable to handle the request, usually due to overload or maintenance.
504
Gateway Timeout
A gateway or proxy did not receive a response from an upstream server in time.
505
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
507
Insufficient Storage
The server cannot store the data needed to complete the request.
508
Loop Detected
The server detected an infinite loop while processing the request.
511
Network Authentication Required
The client must authenticate to the network (captive portal) before accessing the resource.