|
Overview list |
Register and receive a token to access the API. The token will be available in your personal account.
json
xml
csv
xlsx date of update: 2024-08-31 10:07:50
quantity: 74
quantity: 74
| Code | Name | Description | Full description |
| 100 | Continue | continue | The server is satisfied with the initial request information, and the client can continue sending headers. Introduced in HTTP/1.1. |
| 101 | Switching Protocols | protocol switching | The server complies with the client's request and switches protocols as specified in the header field Upgrade. The server sends a response header Upgradeindicating the protocol it has switched to. Introduced in HTTP/1.1. |
| 102 | Processing | processing in progress | The request has been accepted, but it will take a long time to process. Used by the server to prevent the client from breaking the connection due to a timeout. When receiving such a response, the client should reset the timer and wait for the next command in normal mode. Introduced in WebDAV . |
| 103 | Early Hints | early metainformation | Early Hints - used to return part of the headers early when the full response headers cannot be formed quickly. |
| 200 | OK | good | Successful request. If the client requested any data, it is in the header and/or body of the message. Introduced in HTTP/1.0. |
| 201 | Created | created | A new resource was created as a result of the successful execution of the request. The server may specify the addresses (there may be several) of the created resource in the response body, with the preferred address specified in the header Location. The server is recommended to specify the characteristics of the created resource and its addresses in the response body; the format of the response body is determined by the header Content-Type. When processing a request, the new resource must be created before sending the response to the client, otherwise a response with the code should be used 202. Introduced in HTTP/1.0. |
| 202 | Accepted | The request was accepted for processing, but it was not completed. The client does not have to wait for the final message transmission, as a very long process may be started. Introduced in HTTP/1.0. | |
| 203 | Non-Authoritative Information | information is not authoritative | Similar to the response 200, but in this case the information being transmitted was not taken from the primary source (backup, another server, etc.) and therefore may not be relevant. Introduced in HTTP/1.1. |
| 204 | No | Content | The server successfully processed the request, but the response included only headers and no body. The client should not update the document content, but may apply any metadata it received . Introduced in HTTP/1.0. |
| 205 | Reset | Content | The server forces the client to reset the data entered by the user. The server does not transmit the message body and the document does not need to be updated. Introduced in HTTP/1.1. |
| 206 | Partial Content | partial content | The server successfully completed a partial GET request , returning only part of the message. Content-RangeThe server specifies the byte ranges of the content in the header. Special attention should be paid to caching when working with such responses. Introduced in HTTP/1.1. |
| 207 | Multi-Status | multi-status | The server transmits the results of several independent operations at once. They are placed in the message body itself as an XML document with an object multistatus. It is not recommended to place statuses from a series in this object 1xxbecause of their meaninglessness and redundancy. Appeared in WebDAV . |
| 208 | Already | Reported | The DAV binding members were already listed in a previous part (multistatus) of the response and are not included again. |
| 226 | IM Used | The header A-IMfrom the client was successfully received and the server is returning content based on the specified parameters. Introduced in RFC 3229 to supplement the HTTP protocol with delta encoding support . | |
| 300 | Multiple | Choices | There are several options for providing the resource by MIME type , language, or other characteristics at the specified URI. The server sends a list of alternatives with the message, allowing the client or the user to make a choice automatically. Introduced in HTTP/1.0. |
| 301 | Moved | Permanently | The requested document has been permanently moved to the new URI specified in Locationthe header field. If the client stores this URI, it should be replaced with the new one. Some clients behave incorrectly when processing this code. Introduced in HTTP/1.0. |
| 302 | Found | found | Moved Temporarily — The requested document is temporarily available at a different URI, specified in the header field Location. This code can be used, for example, in server-driven content negotiation. |
| 303 | See Other | The document at the requested URI should be requested using the address in Locationthe header field using the method , GETeven though the first resource was requested using a different method. This code was introduced along with the code 307to avoid ambiguity, so that the server could be sure that the next resource would be requested using the method GET. For example, a web page has a text input field for quick navigation and searching. After entering the data, the browser makes a request using the method POST, including the entered text in the message body. If a document with the entered name is found, the server responds with the code , indicating its permanent address 303in the header . Then the browser is guaranteed to request it using the method to get the content. Otherwise, the server simply returns a page with the search results to the client. Introduced in HTTP/1.1. | |
| 304 | Not | Modified | The server returns this code if the client requested the document using the method GET, used the header If-Modified-Sinceor If-None-Matchand the document has not changed since the specified time. In this case, the server message should not contain a body. Introduced in HTTP/1.0. |
| 305 | Use Proxy | use proxy | The requested resource must be accessed through a proxy server whose URI is specified in Locationthe header field. Only HTTP origin servers (not proxies) can use this response code. Introduced in HTTP/1.1. |
| 306 | reserved (code used only in early specifications) | (Reserved) is a response code used in early versions of the specification, now reserved. It is mentioned in RFC 2616 (an update to HTTP/1.1). According to early drafts, the code meant Switch Proxy, instructing the client to change the proxy server used to the one specified by the server in the response header | |
| 307 | Temporary Redirect | temporary redirect | The requested resource is temporarily available at a different URI specified in the Locationheader field. The request method (GET/POST) is not allowed to change. For example, a POST request must be sent to a new URI using the same POST method. This code was introduced along with 303 instead of 302 to avoid ambiguity. Introduced in RFC 2616 (HTTP/1.1 update). |
| 308 | Permanent Redirect | The requested resource has been permanently moved to the new URI specified in Locationthe header field. The request method (GET/POST) is not allowed to change. For example, a POST request must be sent to the new URI using the same POST method. This code was introduced instead of 301 to avoid ambiguity. Introduced in RFC 7238 ( RFC 7538 ). | |
| 400 | Bad Request | incorrect, invalid request | The server detected a syntax error in the client's request. Introduced in HTTP/1.0. |
| 401 | Unauthorized | Authentication is required to access the requested resource . The response header must contain a field WWW-Authenticatewith a list of authentication conditions. In other words, to access the requested resource, the client must identify itself by sending a request, while including a field Authorizationwith the required authentication data in the message header. If the request already includes authorization data, the 401 response means that authorization with them is denied. | |
| 402 | Payment Required - reserved for future use | Expected to be used in the future [ when? ] . Not currently used [ when? ] . This code is intended for paid user services, and it is incorrect to issue it to hosting providers if the site owner has not paid for their services. Reserved since HTTP/1.1. | |
| 403 | Forbidden | not authorized | The server understood the request, but it refuses to fulfill it due to restrictions on the client's access to the specified resource. In other words, the client is not authorized to perform operations with the requested resource. If authentication by means of HTTP is required to access the resource, the server will return a response 401, or 407when using a proxy . Otherwise, the restrictions were set by the server administrator or web application developer and can be anything depending on the capabilities of the software used . In any case, the server should be informed of the reasons for refusing to process the request. The most likely reasons for the restriction are an attempt to access system resources of the web server (for example, files .htaccessor .htpasswd) or files that were closed using configuration files, a requirement for authentication other than HTTP, for example, to access the content management system or a section for registered users, or the server is not satisfied with the client's IP address , for example, when blocking. Introduced in HTTP/1.0. |
| 404 | Not | Found | The most common error when using the Internet, the main reason is a mistake in writing the address of the Web page. The server understood the request, but did not find the corresponding resource at the specified URL. If the server knows that there was a document at this address, then it is advisable to use the code 410 . The response 404can be used instead of 403if it is necessary to carefully hide certain resources from prying eyes. Introduced in HTTP/1.0. |
| 405 | Method Not Allowed | method not supported | The method specified by the client cannot be applied to the current resource. In the response, the server must specify the available methods in the header Allow, separating them with a comma. The server must return this error if the method is known to it, but it is not applicable to the resource specified in the request. If the specified method is not applicable on the entire server, then the code 501(Not Implemented) must be returned to the client. Introduced in HTTP/1.1. |
| 406 | Not | Acceptable | The requested URI does not satisfy the characteristics passed in the header. If the method was not HEAD, the server should return a list of acceptable characteristics for the resource. Introduced in HTTP/1.1. |
| 407 | Proxy Authentication Required | The response is similar to the code, 401except that authentication is performed for the proxy server. The mechanism is similar to identification on the original server. Introduced in HTTP/1.1. | |
| 408 | Request | Timeout | The server has timed out waiting for the transfer from the client. The client can repeat a similar request at any time. For example, such a situation may occur when uploading a large file to the server using the POSTor method PUT. At some point in the transfer, the data source stopped responding, for example, due to damage to the CD or loss of connection with another computer on the local network. While the client does not transfer anything, waiting for a response from it, the connection with the server is maintained. After some time, the server can close the connection on its side to allow other clients to make a request. This response is not returned when the client forcibly stopped the transfer by the user's command or the connection was interrupted for some other reason, since it is no longer possible to send a response. Introduced in HTTP/1.1. |
| 409 | Conflict | conflict | The request cannot be completed because of a conflicting access to the resource. This can happen, for example, when two clients try to modify a resource using the method PUT. Introduced in HTTP/1.1. |
| 410 | Gone | This response is sent by the server if the resource was previously at the specified URL, but was deleted and is now unavailable. In this case, the server does not know the location of the alternative document (for example, a copy). Introduced in HTTP/1.1. | |
| 411 | Length Required | The client must specify Content-Lengthin the request header for the specified resource. Without specifying this field, you should not retry the request to the server at this URI. This response is natural for requests of the POSTand types PUT. For example, if files are downloaded at the specified URI, and the server has a limit on their size. Then it would be wiser to check the header at the very beginning Content-Lengthand immediately refuse the download, than to provoke a meaningless load by breaking the connection when the client actually sends too large a message. Introduced in HTTP/1.1 | |
| 412 | Precondition Failed | condition is false | Returned if none of the conditional header fields (If-Match, etc., see RFC 7232 ) of the request were satisfied. Introduced in HTTP/1.1. |
| 413 | Payload | Too Large | Returned if the server refuses to process the request because the request body is too large. The server may close the connection to stop further transmission of the request. If the problem is temporary, it is recommended to include a header in the server's response Retry-Afterindicating the time after which a similar request can be repeated. Introduced in HTTP/1.1. Previously called "Request Entity Too Large". |
| 414 | URI Too Long | URI too long | The server cannot process the request because the specified URI is too long. This error can be caused, for example, when the client tries to pass long parameters via the method GET, not the method POST. Introduced in HTTP/1.1. Previously called "Request-URI Too Long". |
| 415 | Unsupported Media | Type | Unsupported Media Type — for some reason the server refuses to work with the specified data type with this method. Introduced in HTTP/1.1. |
| 416 | Range Not | Satisfiable | RangeA range outside the resource was specified in a request header field, and the field is missing If-Range. If the client passed a byte range, the server MAY return the actual size in Content-Rangethe header field. This response should not be used when passing. Introduced in RFC 2616 (an update to HTTP/1.1). Previously called "Requested Range Not Satisfiable".multipart/byteranges |
| 417 | Expectation | Failed | For some reason, the server cannot satisfy the value of the Expectrequest header field. Introduced in RFC 2616 (HTTP/1.1 update). |
| 418 | I'm a | teapot | This code was introduced in 1998 as one of the traditional April Fools' jokes by the IETF in RFC 2324, Hyper Text Coffee Pot Control Protocol. This code is supported by most real servers. |
| 526 | Invalid SSL | Certificate | Occurs when the web server's encryption certificate cannot be verified; non-standard CloudFlare code |
| 419 | Authentication Timeout (not in RFC 2616) | usually a CSRF validation error | This code is not in RFC 2616 , it is used as an alternative to the 401 code, which are authenticated but denied access to certain server resources. Typically, the code is returned if the CSRF token is expired or invalid. |
| 421 | Misdirected Request | The request was redirected to a server that is unable to provide a response. | |
| 422 | Unprocessable Entity | The server successfully accepted the request and can work with the specified type of data (for example, the request body contains an XML document with the correct syntax), but there is some logical error that prevents the operation from being performed on the resource. Introduced in WebDAV . | |
| 423 | Locked | The target resource of the request is blocked from having the specified method applied to it. Introduced in WebDAV. | |
| 424 | Failed | Dependency | The current request may depend on another operation being completed successfully. If it fails and the current request cannot be completed because of this, the server returns this code. Introduced in WebDAV. |
| 425 | Too | Early | The server is not prepared to accept the risks of processing "early information". Introduced in RFC 8470 to protect against replay attacks when using 0-RTT in TLS 1.3. |
| 426 | Upgrade Required | upgrade required | The server indicates to the client that it needs to upgrade the protocol. The response header must contain correctly formed Upgradeand fields Connection. Introduced in RFC 2817 to enable the transition to TLS over HTTP. |
| 428 | Precondition | Required | The server tells the client to use condition headers like If-Match. Introduced in RFC 6585. |
| 429 | Too Many Requests | The client attempted to send too many requests in a short time, which may indicate, for example, a DDoS attack attempt. May be accompanied by a Retry-After header, indicating after how long the request can be repeated. Introduced in RFC 6585. | |
| 431 | Request Header Fields Too Large | The headers have exceeded the allowed length. The server is not required to respond with this code; it may simply reset the connection instead. Introduced in RFC 6585. | |
| 449 | Retry With | retry with | Returned by the server if insufficient information is received from the client to process the request. In this case, the field is placed in the response header Ms-Echo-Request. Introduced by Microsoft for WebDAV. |
| 451 | Unavailable For Legal | Reasons | Access to the resource is closed for legal reasons, such as at the request of government authorities or at the request of the copyright holder in the event of copyright infringement. Introduced in the IETF draft by Google, and the error code is a reference to the Ray Bradbury novel Fahrenheit 451. It was added to the standard on December 21, 2015 |
| 499 | Client Closed Request | the client closed the connection | Client Closed Request is a non-standard code proposed and used by nginx for cases when the client closed the connection while nginx was processing the request. |
| 500 | Internal Server | Error | Any internal server error that does not fall within the scope of other errors of the class. Introduced in HTTP/1.0. |
| 501 | Not | Implemented | The server does not support the capabilities required to process the request. A typical response for cases where the server does not understand the method specified in the request. If the server knows the method, but it is not applicable to the resource, then the response should be returned 405. Introduced in HTTP/1.0. |
| 502 | Bad Gateway | bad, erroneous gateway | The server, while acting as a gateway or proxy, received an invalid response message from an upstream server. Introduced in HTTP/1.0. |
| 503 | Service | Unavailable | The server is temporarily unable to process requests due to technical reasons (maintenance, overload, etc.). In the Retry-Afterheader field, the server can specify a time after which the client is recommended to repeat the request. Although it seems obvious to immediately break the connection during an overload, it may be more effective to set a large value for the field Retry-Afterto reduce the frequency of redundant requests. Introduced in HTTP/1.0. |
| 504 | Gateway Timeout | gateway not responding | The server, acting as a gateway or proxy, did not wait for a response from the upstream server to complete the current request. Introduced in HTTP/1.1. |
| 505 | HTTP Version Not | Supported | The server does not support or refuses to support the HTTP protocol version specified in the request. Introduced in HTTP/1.1. |
| 506 | Variant Also | Negotiates | Due to a misconfiguration, the selected variant points to itself, causing the binding process to fail. Experimental. Introduced in RFC 2295 to extend the HTTP protocol with Transparent Content Negotiation. |
| 507 | Insufficient Storage | There is not enough storage to fulfill the current request. The problem may be temporary. Introduced in WebDAV . | |
| 508 | Loop | Detected | The operation was cancelled because the server detected an infinite loop while processing a request without depth limitation. Introduced in WebDAV. |
| 509 | Bandwidth Limit Exceeded | Used when the web site exceeds its allotted traffic consumption limit. In this case, the site owner should contact their hosting provider. At the moment, this code is not described in any RFC and is used only by the "bw/limited" module, which is part of the cPanel hosting control panel , where it was introduced. | |
| 510 | Not | Extended | The server does not have the extension that the client wants to use. The server may optionally pass information about the extensions available to it. Introduced in RFC 2774 to supplement the HTTP protocol with extension support. |
| 511 | Network Authentication Required | network authentication required | This response is sent not by the server to which the request was addressed, but by an intermediary server — for example, a provider's server — if the client must first authenticate on the network, such as entering a password for a paid Internet access point. The response body is expected to return a web-based authorization form or a redirect to it. Introduced in draft RFC 6585. |
| 520 | Unknown Error | unknown error | Unknown Error, occurs when the CDN server was unable to handle a web server error; non-standard CloudFlare code . |
| 521 | Web | Server Is Down | Web Server Is Down, occurs when CDN connections are rejected by the web server; non-standard CloudFlare code . |
| 522 | Connection Timed Out | connection not responding | Connection Timed Out, occurs when the CDN failed to connect to the web server; non-standard CloudFlare code . |
| 523 | Origin Is | Unreachable | Origin Is Unreachable, occurs when the web server is unreachable; non-standard CloudFlare code . |
| 524 | A Timeout | Occurred | Occurs when the connection between the CDN server and the web server times out ; non-standard CloudFlare code . |
| 525 | SSL Handshake | Failed | Occurs when the SSL handshake between the CDN server and the web server fails; non-standard CloudFlare code . |