The server has received the initial part of the request and the client should proceed to send the remainder.
1xx
RFC 9110
false
101
101
Switching Protocols
The server is switching to the protocol requested by the client via the Upgrade header.
1xx
RFC 9110
false
102
102
Processing
The server has received and is processing the request, but no response is available yet. Used in WebDAV to prevent client timeouts.
1xx
RFC 2518
false
103
103
Early Hints
The server is sending preliminary headers to allow the client to preload resources before the final response.
1xx
RFC 8297
false
200
200
OK
The request succeeded. The meaning of the success depends on the HTTP method used.
2xx
RFC 9110
false
201
201
Created
The request succeeded and a new resource was created as a result, typically in response to a POST or PUT.
2xx
RFC 9110
false
202
202
Accepted
The request has been accepted for processing, but the processing has not been completed and may not yet have started.
2xx
RFC 9110
false
203
203
Non-Authoritative Information
The request succeeded but the enclosed payload has been modified by a transforming proxy from the origin server's 200 response.
2xx
RFC 9110
false
204
204
No Content
The request succeeded but there is no content to send in the response body. Often used for successful DELETE or PUT operations.
2xx
RFC 9110
false
205
205
Reset Content
The request succeeded and the server asks the client to reset the document view that caused the request.
2xx
RFC 9110
false
206
206
Partial Content
The server is delivering only part of the resource due to a Range header sent by the client.
2xx
RFC 9110
false
207
207
Multi-Status
A WebDAV response conveying information about multiple resources where multiple status codes might be appropriate.
2xx
RFC 4918
false
208
208
Already Reported
Used inside a WebDAV DAV:propstat element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.
2xx
RFC 5842
false
226
226
IM Used
The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
2xx
RFC 3229
false
300
300
Multiple Choices
The request has more than one possible response and the user or user agent should choose one of them.
3xx
RFC 9110
false
301
301
Moved Permanently
The requested resource has been permanently moved to a new URI. Future requests should use the new URI.
3xx
RFC 9110
false
302
302
Found
The requested resource temporarily resides at a different URI. The client should continue to use the original URI for future requests.
3xx
RFC 9110
false
303
303
See Other
The server is redirecting the client to a different resource using a GET request, typically after a POST operation.
3xx
RFC 9110
false
304
304
Not Modified
The resource has not been modified since the version specified by the conditional headers. The client can use its cached copy.
3xx
RFC 9110
false
305
305
Use Proxy
The requested resource must be accessed through the proxy specified in the Location header. Deprecated due to security concerns.
3xx
RFC 9110
true
307
307
Temporary Redirect
The requested resource temporarily resides at a different URI. Unlike 302, the request method must not change when reissuing the request.
3xx
RFC 9110
false
308
308
Permanent Redirect
The resource has been permanently moved to a new URI. Unlike 301, the request method must not change when following the redirect.
3xx
RFC 9110
false
400
400
Bad Request
The server cannot process the request due to something perceived to be a client error, such as malformed syntax or invalid framing.
4xx
RFC 9110
false
401
401
Unauthorized
The request requires user authentication. The client must provide valid credentials to access the resource.
4xx
RFC 9110
false
402
402
Payment Required
Reserved for future use. Originally intended for digital payment schemes, but not widely used in practice.
4xx
RFC 9110
false
403
403
Forbidden
The server understood the request but refuses to authorize it. Authentication will not help; the client lacks permission.
4xx
RFC 9110
false
404
404
Not Found
The server cannot find the requested resource. The URI may be incorrect or the resource may no longer exist.
4xx
RFC 9110
false
405
405
Method Not Allowed
The HTTP method used is not supported for the requested resource. The response includes an Allow header listing valid methods.
4xx
RFC 9110
false
406
406
Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.
4xx
RFC 9110
false
407
407
Proxy Authentication Required
The client must first authenticate with the proxy before the request can proceed. Similar to 401 but for proxy servers.
4xx
RFC 9110
false
408
408
Request Timeout
The server timed out waiting for the request. The client did not produce a request within the time the server was prepared to wait.
4xx
RFC 9110
false
409
409
Conflict
The request conflicts with the current state of the target resource, such as an edit conflict in a version-controlled system.
4xx
RFC 9110
false
410
410
Gone
The requested resource is no longer available at the server and no forwarding address is known. This condition is considered permanent.
4xx
RFC 9110
false
411
411
Length Required
The server refuses to accept the request without a defined Content-Length header.
4xx
RFC 9110
false
412
412
Precondition Failed
One or more conditions given in the request header fields evaluated to false when tested on the server.
4xx
RFC 9110
false
413
413
Content Too Large
The request payload is larger than the server is willing or able to process. The server may close the connection.
4xx
RFC 9110
false
414
414
URI Too Long
The request target URI is longer than the server is willing to interpret, often caused by excessive query string data.
4xx
RFC 9110
false
415
415
Unsupported Media Type
The server refuses to accept the request because the payload format or content encoding is not supported for the target resource.
4xx
RFC 9110
false
416
416
Range Not Satisfiable
The range specified in the Range header cannot be fulfilled. The range may be outside the extent of the target resource's data.
4xx
RFC 9110
false
417
417
Expectation Failed
The expectation given in the request's Expect header could not be met by the server.
4xx
RFC 9110
false
418
418
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot. Defined by the Hyper Text Coffee Pot Control Protocol.
4xx
RFC 2324
false
421
421
Misdirected Request
The request was directed at a server that is not able to produce a response, such as a connection reuse issue.
4xx
RFC 9110
false
422
422
Unprocessable Content
The server understands the content type and syntax of the request but was unable to process the contained instructions.
4xx
RFC 9110
false
423
423
Locked
The source or destination resource of a method is locked. Used in WebDAV when a resource cannot be modified.
4xx
RFC 4918
false
424
424
Failed Dependency
The method could not be performed on the resource because the requested action depended on another action that failed.
4xx
RFC 4918
false
425
425
Too Early
The server is unwilling to risk processing a request that might be replayed, typically when using TLS Early Data (0-RTT).
4xx
RFC 8470
false
426
426
Upgrade Required
The server refuses to perform the request using the current protocol but may do so after the client upgrades to a different protocol.
4xx
RFC 9110
false
428
428
Precondition Required
The origin server requires the request to be conditional to prevent lost update conflicts on concurrent modifications.
4xx
RFC 6585
false
429
429
Too Many Requests
The user has sent too many requests in a given amount of time. Used for rate limiting.
4xx
RFC 6585
false
431
431
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large, either individually or in total.
4xx
RFC 6585
false
451
451
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand. Named after Fahrenheit 451.
4xx
RFC 7725
false
500
500
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
5xx
RFC 9110
false
501
501
Not Implemented
The server does not support the functionality required to fulfill the request. Typically returned for unrecognized HTTP methods.
5xx
RFC 9110
false
502
502
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from an upstream server.
5xx
RFC 9110
false
503
503
Service Unavailable
The server is currently unable to handle the request due to temporary overloading or scheduled maintenance.
5xx
RFC 9110
false
504
504
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
5xx
RFC 9110
false
505
505
HTTP Version Not Supported
The server does not support the major version of HTTP that was used in the request.
5xx
RFC 9110
false
506
506
Variant Also Negotiates
The server has an internal configuration error where the chosen variant resource is itself configured to engage in content negotiation.
5xx
RFC 2295
false
507
507
Insufficient Storage
The server is unable to store the representation needed to complete the request. Used in WebDAV.
5xx
RFC 4918
false
508
508
Loop Detected
The server detected an infinite loop while processing the request. Used in WebDAV with Binding extensions.
5xx
RFC 5842
false
510
510
Not Extended
The server requires further extensions to the request in order to fulfill it. The client should include the required extension declarations.
5xx
RFC 2774
false
511
511
Network Authentication Required
The client needs to authenticate to gain network access, typically used by captive portals intercepting network traffic.