Consulte o significado de códigos HTTP 2xx, 3xx, 4xx e 5xx. Útil para APIs, redirecionamentos, páginas ausentes e diagnóstico.
Tip: Press Ctrl+F to search quickly.| Http status code | Status Code Meaning |
|---|---|
| 100 | The client should continue to send the request. The interim response is to inform the client that some of its requests have been received by the server and have not been rejected. The client should continue to send the remainder of the request or, if the request is completed, ignore the response. The server must send a final response to the client after the request has been completed. |
| 101 | The server has understood the client's request and will notify the client via Upglade header to use a different protocol to complete the request. After sending this last empty line of response, the server will switch to the agreements defined in Upglade header. Similar measures should be taken only if it is more advantageous to switch to the new protocol. For example, switching to the new HTTP version is better than the old version, or switching to a real-time and synchronized agreement to transmit resources using such characteristics. |
| 102 | The status code extended by WebDAV (RFC 2518) will be continued. |
| 200 | The request is successful and the desired response head or data body of the request returns with it. |
| 201 | The request has been fulfilled, and a new resource has been created in response to the request, and its URL has returned with the Location header information. |
| 202 | The server has accepted the request, but it has not yet been processed. As it may have been rejected, the request may or may not eventually be executed. There is no easier way to send the status code than in the event of an animate. The purpose of the return of the 202 status code is to allow the server to accept requests from other processes (e.g., a batch-based operation that is performed only once a day) without having to keep the client connected to the server until the batch is fully completed. The response to the request for processing and returning the 202 status code should include in the returned entity some instructions to process information on the current state, as well as pointing to the processing status monitor or the guidance for the status prediction, so that the user can estimate whether the operation has been completed. |
| 203 | The server has successfully processed the request, but the returned entity's head meta-information is not a valid set on the original server, but a copy of it from local or third parties. The current information may be a subset of the original version or a superset. For example, metadata containing resources may lead the original server to know the meta-information super. The use of this status code is not necessary and is only appropriate if the response does not return 200 OK. |
| 204 | The server successfully processed the request without having to return any physical content and wishing to return updated meta-information. The response may return new or updated meta-information in the form of the entity ' s head. If these head-informations exist, they should correspond to the requested variable. If the client is a browser, the user browser should keep the requested page and do not produce any changes in the document view, even though the new or updated meta-information should be applied to the document in the user browser activity view, according to the specifications. Since 204 responses are forbidden to contain any information, it always ends with the first empty line after the message. |
| 205 | The server successfully processed the request and did not return any content. Unlike the 204 response, the responder who returned this status code resets the document view. The response is primarily used to reset the form immediately after receiving the user ' s input so that the user can easily start another entry. As with the 204 response, the response is forbidden to contain any message and ends with the first blank line after the message. |
| 206 | The server has successfully processed some of the GT requests. If the HTTP downloading tool, such as FlashGet or Thunder, uses this type of response to achieve breakpoints or to divide a large document into multiple downloads at the same time. The request must contain the Range headline information to indicate the content that the client wishes to receive and may include If-Range as a condition for the request. If the response contains any of the following headlines: Content-Range indicates the scope of the returned content of the response; if it is Content-Type downloads multiple sections of the response to the response, the same request should be responded to 200 other entities; if it does not provide a response to the text of the request, the CO6-Couch-Ronge will be able to return to the content of the instruction. If the response contains the exact content of the request, then it will not be available to the other entities. |
| 207 | The status code extended by WebDAV (RFC 2518) will represent the subsequent body of the message as an XML message and may contain a series of independent response codes depending on the number of previous sub-requests. |
| 300 | The requested resource has a range of options for feedback, each with its own specific address and browser-driven bargaining information. Users or browsers are able to re-direct themselves to a preferred address. Unless this is a HEAD request, the response should include an entity with a resource identity and a list of addresses from which the user or browser selects the most appropriate re-directive address. The format of this entity is determined by the format defined by the Centre-Type. The browser may automatically make the most appropriate choice, depending on the format of the response and the browser’s own capabilities. Of course, RFC 2616 does not specify how this automatic choice should be made. If the server itself has a first-chosen feedback option, the URL of the feedback should be identified in the Location; the browser may use this Location value as an automatic re-direction address. |
| 301 | The requested resource has been permanently moved to a new location, and any future references to this resource should use one of several URLs returned by the response. If possible, the client with the link editing function should automatically change the address requested to the address returned from the server. This response is also a cache unless additional designation is made. The new permanent URL should return in the Location domain. Unless this is a HEAD request, the responding entity should include hyperlinks and a short description pointing to the new URL. If this is not a GEET or HEAD request, the browser is prohibited from automatically re-directing unless it is confirmed by the user that the conditions of the request may change as a result. Note: For some browsers using the HTTP/1.0 protocol, the next re-directive request will become the GET mode if they send a 301 response. |
| 302 | The requested resources are now responding to requests from different URLs on an ad hoc basis. Since such a reorientation is temporary, the client should continue to send requests after the original address. This response can only occur if designated in Cache-Control or Expicres. The new temporary URL should return in the Location domain. Unless this is a HEAD request, the responding entity should include hyperlinks and a brief description pointing to the new URI. If this is not a GET or HEAD request, the browser is prohibited from automatically re-directing unless it is confirmed by the user that the conditions of the request may change as a result. |
| 303 | The response to the current request can be found on another URL, and the client should access the resource by means of the GEET. This method exists mainly to allow the output of POST, which is activated by script, to be redirected to a new resource. This new URL is not a substitute for the original resource. At the same time, 303 responded to the prohibition of caches. Of course, the second request (redirection) may be cached. The new URL should return in the Location domain. Unless this is a HEAD request, the responding entity should include hyperlinks and a brief description pointing to the new URL. Note that many former HTTP/1.1 browsers do not properly understand the 303 state. If interaction with these browsers needs to be considered, the 302 code should be competent, because most browsers should be able to handle 302 responses precisely the same way the client should be asked to handle 303 responses. |
| 304 | If the client sends a conditioned GEET request and the request is allowed, and the contents of the document (since the last visit or according to the terms of the request) have not changed, the server should return to the status code.304 The response to the prohibition on inclusion of the message should always end with the first empty line after the message. The response must contain the following headline: Date, unless the server does not have a clock. If the server does not follow the rules, the proxy server and the client themselves can add the Date field to the response to the received response (as provided for in RFC 2068). If the response to the request uses a strong hold check (as specified in RFC 2068), the current response mechanism should not include any other entity; otherwise (e.g., a request by GET with a condition requires a weak check) if the response should have been to the other entity. Expires, Cache-Control, and Vary, if the response to the current submission does not contain a slow-down request for an entity to update, then it would have been less than one. |
| 305 | The requested resource must be accessed by a designated agent. The local Location domain will give the specified agent's URL information, and the recipient will have to repeat a separate request and this agent will be able to access the corresponding resources. Only the original server can create 305 responses. Note: RFC 2068 does not explicitly respond to a separate request for re-direction and can only be created by the original server. |
| 306 | In the latest version of the Code, 306 status codes are no longer used. |
| 307 | The requested resource is now responding to requests from different URLs on a temporary basis. Since such reorientation is temporary, the client should continue to send requests to the original address. This response can only occur if specified in the Cache-Control or Expires. The new temporary URL should return in the Location domain of the response. Unless this is a HEAD request, the responding entity should include hyperlinks and a brief description pointing to the new URL. Since some browsers cannot identify 307 responses, the necessary information needs to be added so that the user can understand and send a request for access to the new URL. If this is not a GET or HEAD request, the browser is prohibited from automatically redirecting unless it is confirmed by the user that the request is subject to a change in the conditions. |
| 400 | 1 There is an error in semantics, and the current request cannot be understood by the server. Unless modified, the client should not repeat the request. |
| 401 | The current request requires user authentication. The response must include a WWW-Authentity header that is suitable for the requested resource to ask for user information. The client can repeat a request containing the appropriate Autoration header information. If the current request already contains the Autoration certificate, then the 401 response represents the server certification that has been rejected. If the 401 response contains the same authentication query as the previous one, and the browser has tried at least once, the browser should show the user the entity information contained in the response, because this entity information may contain relevant diagnostic information. See RFC 2617. |
| 402 | The status code is reserved for possible future needs. |
| 403 | The server has understood the request, but refuses to execute it. Unlike 401, authentication does not provide any help, and this request should not be repeated. If this is not a HEAD request, and the server wishes to be able to explain why it cannot be executed, then the reason for the refusal should be described within the entity. The server can also return a 404 response, if it does not want the client to get any information. |
| 404 | The request failed, and the desired resources were not found on the server. There is no information to tell the user whether the situation is temporary or permanent. If the server is aware of the situation, the 410 status code should be used to inform the old resources that, because of some internal configuration problems, they are permanently unavailable and that there is no address that can be jumped. |
| 405 | The request method specified in the request line cannot be used to request the corresponding resource. The response must return a list of Allow headers to indicate how the current resource is acceptable. Given that the PUT, the DELETE method handles the resources on the server, the vast majority of the web servers do not support or do not allow the above-mentioned request method under default configuration, such requests return 405 errors. |
| 406 | Unless this is a HEAD request, the response should return to an entity that contains a list of the most suitable physical features and addresses from which the user or browser can select. The format of the entity is determined by the type of media defined in the Content-Type header. The browser can make the best choice of its own depending on the format and its abilities. However, the norm does not define any criteria for such automatic selection. |
| 407 | Similar to the 401 response, the client must authenticate on the proxy server. The proxy server must return a Proxy-Authenticate for an identity query. The client can return a Proxy-Authorization header for authentication. See RFC 2617. |
| 408 | The client can submit the request again at any time without any change. |
| 409 | Because of the conflict with the current state of the requested resource, the request cannot be fulfilled. The code allows only for use in cases where the user is deemed to be able to resolve the conflict and will resubmit a new request. The response should contain sufficient information to enable the user to discover the source of the conflict. Conflict usually occurs in the processing of PUT requests. For example, in the context of a version check, the information attached to a request submitted by a PUT to modify a given resource conflicts with a previous (third party) request, then the server should return a 409 error and inform the user that the request cannot be completed. At this time, the responding entity is likely to contain a comparison of the two versions of the conflict, so that the user can resubmit and return to a later version. |
| 410 | The requested resource is no longer available on the server and there is no known forwarding address. This situation should be considered permanent. If possible, the client with the link editing function should remove all references to this address after obtaining permission from the user. If the server does not know or cannot determine whether the condition is permanent, then the 404 status code should be used. The response is cacheable unless additional information is provided. |
| 411 | The server refuses to accept the request without defining the Content-Length head. After adding a valid Content-Length header that indicates the length of the requested body, the client can submit the request again. |
| 412 | The server does not satisfy one or more of the prerequisites when verifying that the request starts in the front field. This status code allows the client to set preconditions in the requested meta-information (request for header field data) when acquiring the resource, thereby avoiding the application of the request method to a resource other than its desired content. |
| 413 | The server refuses to process the current request because the entity data submitted by the request exceeds the scope that the server is willing or able to process. In this case, the server can close the connection to prevent the client from continuing to send the request. |
| 414 | The length of the requested URL exceeds the length that the server can explain, and therefore the server refuses to provide the requested service. This is less common, as is often the case when the form that should have been submitted using the POST method is turned into a GET method, leading to an excessive length of the query string (Query Spring). Redirecting the URL “black hole”, such as using the old URL as part of the new URL each re-direction, leads to an excessive length of the URL after several re-directions. The client is trying to use a security gap in some servers to attack the server. Such servers use a fixed length buffer to read or operate the URL of the request, and when the parameters after the GET exceed a certain value, the buffer zone may spill, resulting in the implementation of an arbitrary code. |
| 415 | With regard to the methodology for the current request and the resources requested, the entity that submitted the request was not the format supported on the server and the request was therefore rejected. |
| 416 | If the request contains Lange's headline, and any data range specified in Lange does not overlap with the current resource range, and if If-Range's headline is not defined in the request, the server should return the 416 status code. If Lange uses a byte range, then this means that the first byte position of all data ranges requested exceeds the current resource length. The server should also include a Contant-Range entity head, while returning the 416 status code, to indicate the length of the current resource. This response is also prohibited. |
| 417 | The expected content specified in the first Expect cannot be satisfied by the server, or the server is a proxy server with clear evidence that the Expect content cannot be satisfied at the next node of the current route. |
| 421 | The number of connections from the IP address of the current client to the server exceeds the maximum number of server permits. Usually, the IP address here refers to the client ' s address (e.g. the user ' s gateway or proxy server address) seen from the server. In this case, the number of connections may involve more than one end user. |
| 422 | The number of connections from the IP address of the current client to the server exceeds the maximum number of server permits. Usually, the IP address here refers to the client ' s address (e.g. the user ' s gateway or proxy server address) seen from the server. In this case, the number of connections may involve more than one end user. |
| 422 | The request is correctly formatted, but cannot be responded to due to semantic errors. (RFC 4918 WebDAV) 423 Locked's current resource is locked. (RFC 4918 WebDAV) |
| 424 | An error in a previous request led to the failure of the current request, such as PROPPATCH. (RFC 4918 WebDAV) |
| 425 | Definition in draft WebDav Advanced Conventions, but not in the WebDAV Sequencing Agreement (RFC 3658). |
| 426 | The client should switch to TLS/1.0. (RFC 2817) |
| 449 | By Microsoft, delegates requested that a re-test should be conducted after the proper operation had been completed. |
| 500 | The server encountered an unforeseen condition that prevented it from completing the processing of requests. In general, the problem arose when the server code was wrong. |
| 501 | The server does not support a function that is required for the current request. |
| 502 | When servers working as gateways or agents attempt to execute requests, invalid responses are received from upstream servers. |
| 503 | The server is currently unable to process the request because of temporary server maintenance or overloading. This situation is temporary and will be restored after a certain period of time. If a delay can be anticipated, the response can include a Retry-After header to mark the delay. If this Retry-After information is not given, the client should handle it in a 500-response way. Note: The existence of the 503 status code does not mean that the server must use it at the time of overload. Some servers simply wish to reject the client's connection. |
| 504 | Servers that work as gateways or proxy do not receive responses in time from upstream servers (URI-identified servers such as HTTP, FTP, LDAP) or auxiliary servers (e.g. DNS). Note: Some proxy servers return 400 or 500 errors when DNS queries are timed out |
| 505 | The server does not support, or refuses to support, the HTTP version used in the request. This implies that the server is unable or unwilling to use the same version as the client. The response should include an entity that describes why the version is not supported and which agreements are supported by the server. |
| 506 | Expanded by the Transparency Content Consultation Agreement (RFC 2295), there was an internal configuration error on behalf of the server: the requested consultation variable meta resources were allocated to use themselves in transparent content consultations and therefore not a suitable focus in a consultative process. |
| 507 | The server cannot store what is necessary to complete the request. This situation is considered temporary. |
| 509 | The server meets bandwidth limits. This is not an official state code, but it is still widely used. |
| 510 | The strategy needed to access resources has not been met. (RFC 2774) |