|
1xx Informational |
|
Request received, continuing process. |
| 100 |
Continue |
Standard |
Server received request headers, client should proceed to send request body. |
| 101 |
Switching Protocols |
Standard |
Server is switching protocols as requested by the client. |
| 102 |
Processing (WebDAV) |
Standard (RFC 2518) |
Server has received and is processing the request, but no response is available yet. |
| 103 |
Early Hints |
Standard (RFC 8297) |
Used to return some response headers before final HTTP message. |
|
2xx Success |
|
The action was successfully received, understood, and accepted. |
| 200 |
OK |
Standard |
Request succeeded. |
| 201 |
Created |
Standard |
Request succeeded, and a new resource was created as a result. |
| 202 |
Accepted |
Standard |
Request has been accepted for processing, but processing is not complete. |
| 203 |
Non-Authoritative Information |
Standard |
Returned meta-information is from a local or third-party copy, not origin server. |
| 204 |
No Content |
Standard |
Server successfully processed the request, but is not returning any content. |
| 205 |
Reset Content |
Standard |
Server successfully processed the request, asks that the requester reset its document view. |
| 206 |
Partial Content |
Standard |
Server is delivering only part of the resource due to a range header. |
| 207 |
Multi-Status (WebDAV) |
Standard (RFC 4918) |
Conveys information about multiple resources in situations where multiple status codes are appropriate. |
| 208 |
Already Reported (WebDAV) |
Standard (RFC 5842) |
Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly. |
| 226 |
IM Used (HTTP Delta Encoding) |
Standard (RFC 3229) |
Server has fulfilled a GET request for the resource, response is a representation of the result of one or more instance-manipulations applied to the current instance. |
|
3xx Redirection |
|
Further action must be taken in order to complete the request. |
| 300 |
Multiple Choices |
Standard |
Request has more than one possible response. User-agent or user should choose one. |
| 301 |
Moved Permanently |
Standard |
The URL of the requested resource has been changed permanently. |
| 302 |
Found |
Standard |
The URL of the requested resource has been changed temporarily. |
| 303 |
See Other |
Standard |
Server sent this response to direct the client to get the requested resource at another URI with a GET request. |
| 304 |
Not Modified |
Standard |
Used for caching purposes. Tells the client that the response has not been modified. |
| 305 |
Use Proxy (Deprecated) |
Standard (Deprecated) |
Defined in a previous version, is deprecated due to security concerns. |
| 307 |
Temporary Redirect |
Standard |
Server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. |
| 308 |
Permanent Redirect |
Standard (RFC 7538) |
Resource is now permanently located at another URI, specified by the Location header. Same semantics as 301 but does not allow changing the request method. |
|
4xx Client Error |
|
The request contains bad syntax or cannot be fulfilled. |
| 400 |
Bad Request |
Standard |
Server could not understand the request due to invalid syntax. |
| 401 |
Unauthorized |
Standard |
Authentication is needed to get the requested response. |
| 402 |
Payment Required |
Standard |
Reserved for future use. Intended for use in digital payment systems. |
| 403 |
Forbidden |
Standard |
Client does not have access rights to the content. |
| 404 |
Not Found |
Standard |
Server cannot find the requested resource. |
| 405 |
Method Not Allowed |
Standard |
Request method is known by the server but is not supported by the target resource. |
| 406 |
Not Acceptable |
Standard |
Server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers. |
| 407 |
Proxy Authentication Required |
Standard |
Similar to 401, but authentication must be done by a proxy. |
| 408 |
Request Timeout |
Standard |
Server would like to shut down this unused connection. |
| 409 |
Conflict |
Standard |
Request conflicts with the current state of the server. |
| 410 |
Gone |
Standard |
Requested content has been permanently deleted from server. |
| 411 |
Length Required |
Standard |
Server rejected the request because the Content-Length header field is not defined and the server requires it. |
| 412 |
Precondition Failed |
Standard |
Client has indicated preconditions in its headers which the server does not meet. |
| 413 |
Payload Too Large |
Standard |
Request entity is larger than limits defined by server. |
| 414 |
URI Too Long |
Standard |
The URI requested by the client is longer than the server is willing to interpret. |
| 415 |
Unsupported Media Type |
Standard |
Media format of the requested data is not supported by the server. |
| 416 |
Range Not Satisfiable |
Standard |
The range specified by the Range header field cannot be fulfilled. |
| 417 |
Expectation Failed |
Standard |
The expectation indicated by the Expect request header field could not be met. |
| 418 |
I'm a teapot |
Standard (RFC 2324, April Fools') |
Server refuses the attempt to brew coffee with a teapot. |
| 421 |
Misdirected Request |
Standard (RFC 7540) |
Request was directed at a server that is not able to produce a response. |
| 422 |
Unprocessable Entity (WebDAV) |
Standard (RFC 4918) |
Request was well-formed but was unable to be followed due to semantic errors. |
| 423 |
Locked (WebDAV) |
Standard (RFC 4918) |
The resource that is being accessed is locked. |
| 424 |
Failed Dependency (WebDAV) |
Standard (RFC 4918) |
Request failed due to failure of a previous request. |
| 425 |
Too Early |
Standard (RFC 8470) |
Server is unwilling to risk processing a request that might be replayed. |
| 426 |
Upgrade Required |
Standard |
Server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. |
| 428 |
Precondition Required |
Standard (RFC 6585) |
Origin server requires the request to be conditional. |
| 429 |
Too Many Requests |
Standard (RFC 6585) |
User has sent too many requests in a given amount of time ("rate limiting"). |
| 431 |
Request Header Fields Too Large |
Standard (RFC 6585) |
Server is unwilling to process the request because its header fields are too large. |
| 444 |
Connection Closed Without Response |
Non-Standard (Nginx) |
Nginx internal code to instruct the server to close the connection without sending a response header. |
| 451 |
Unavailable For Legal Reasons |
Standard (RFC 7725) |
Client requested a resource that cannot legally be provided. |
| 499 |
Client Closed Request |
Non-Standard (Nginx) |
Nginx internal code used when the client terminates the connection while Nginx is processing the request. |
|
5xx Server Error |
|
The server failed to fulfil an apparently valid request. |
| 500 |
Internal Server Error |
Standard |
Server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 |
Not Implemented |
Standard |
Request method is not supported by the server and cannot be handled. |
| 502 |
Bad Gateway |
Standard |
Server, while acting as a gateway or proxy, received an invalid response from the upstream server. |
| 503 |
Service Unavailable |
Standard |
Server is not ready to handle the request (overloaded or down for maintenance). |
| 504 |
Gateway Timeout |
Standard |
Server, while acting as a gateway or proxy, did not get a response in time from the upstream server. |
| 505 |
HTTP Version Not Supported |
Standard |
The HTTP version used in the request is not supported by the server. |
| 506 |
Variant Also Negotiates |
Standard (RFC 2295) |
Server has an internal configuration error: transparent content negotiation for the request results in a circular reference. |
| 507 |
Insufficient Storage (WebDAV) |
Standard (RFC 4918) |
Server is unable to store the representation needed to complete the request. |
| 508 |
Loop Detected (WebDAV) |
Standard (RFC 5842) |
Server detected an infinite loop while processing the request. |
| 510 |
Not Extended |
Standard (RFC 2774) |
Further extensions to the request are required for the server to fulfill it. |
| 511 |
Network Authentication Required |
Standard (RFC 6585) |
Client needs to authenticate to gain network access (used by captive portals). |
| 520 |
Web Server Returned an Unknown Error |
Non-Standard (Cloudflare) |
Cloudflare specific: Origin server returned an empty, unknown, or unexpected response. |
| 521 |
Web Server Is Down |
Non-Standard (Cloudflare) |
Cloudflare specific: Origin server has refused the connection from Cloudflare. |
| 522 |
Connection Timed Out |
Non-Standard (Cloudflare) |
Cloudflare specific: Cloudflare could not negotiate a TCP handshake with the origin server. |
| 523 |
Origin Is Unreachable |
Non-Standard (Cloudflare) |
Cloudflare specific: Cloudflare could not reach the origin server. |
| 524 |
A Timeout Occurred |
Non-Standard (Cloudflare) |
Cloudflare specific: Cloudflare connected to origin, but origin did not provide response before timeout. |
| 525 |
SSL Handshake Failed |
Non-Standard (Cloudflare) |
Cloudflare specific: Cloudflare could not negotiate an SSL/TLS handshake with the origin server. |
| 526 |
Invalid SSL Certificate |
Non-Standard (Cloudflare) |
Cloudflare specific: Cloudflare could not validate the SSL certificate on the origin web server. |
| 530 |
Origin DNS Error |
Non-Standard (Cloudflare) |
Cloudflare specific: Typically seen with 1xxx errors, indicates DNS resolution issue at origin. |
| 561 |
Unauthorized |
Non-Standard (AWS ELB) |
AWS Elastic Load Balancer specific: Error related to authentication with Identity Provider or WAF. |
