PCTOOLSIntroduction
HTTP Status Code
Some common status codes are: 200 - The server successfully returned the webpage 404 - The requested webpage does not exist 503 - Service Unavailable
All Status Explanations:
| Status Code | Status Code Details |
|---|---|
| 100 | （Continue） The server has received the request headers and the client should proceed to send the request body. |
| 101 | （Switching Protocols） The requester has asked the server to switch protocols and the server has agreed to do so. |
| 102 | This code indicates that the server has received and is processing the request, but no response is available yet. (WebDAV; RFC 2518) |
| 200 | （OK） The request has succeeded. |
| 201 | （Created） The request has been fulfilled, resulting in the creation of a new resource. |
| 202 | （Accepted） The request has been accepted for processing, but the processing has not been completed. |
| 203 | （Non-Authoritative Information） The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response. |
| 204 | （No Content） The server successfully processed the request and is not returning any content. |
| 205 | （Reset Content） The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view. |
| 206 | （Partial Content） The server is delivering only part of the resource (byte serving) due to a range header sent by the client. |
| 208 | The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again. (WebDAV; RFC 5842) |
| 226 | （IM Used） The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. (RFC 3229) |
| 300 | （Multiple Choices） Indicates multiple options for the resource from which the client may choose. |
| 301 | （Moved Permanently） This and all future requests should be directed to the given URI. |
| 302 | （Found） Tells the client to look at another URL. 302 has been superseded by 303 and 307. |
| 303 | （See Other） The response to the request can be found under another URI using a GET method. |
| 304 | （Not Modified） Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. |
| 305 | （Use Proxy） The requested resource is available only through a proxy, the address for which is provided in the response. |
| 307 | （Temporary Redirect） In this case, the request should be repeated with another URI; however, future requests should still use the original URI. |
| 308 | （Permanent Redirect） The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change. |
| 400 | （Bad Request) The server cannot or will not process the request due to an apparent client error. |
| 401 | (Unauthorized) Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. |
| 402 | Reserved for future use. |
| 403 | （Forbidden) The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource. |
| 404 | （Not Found) The requested resource could not be found but may be available in the future. |
| 405 | （Method Not Allowed) A request method is not supported for the requested resource. |
| 406 | （Not Acceptable) The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. |
| 407 | （Proxy Authentication Required) The client must first authenticate itself with the proxy. |
| 408 | （Request Timeout) The server timed out waiting for the request. |
| 409 | （Conflict) Indicates that the request could not be processed because of conflict in the current state of the resource. |
| 410 | （Gone) Indicates that the resource requested is no longer available and will not be available again. |
| 411 | （Length Required) The request did not specify the length of its content, which is required by the requested resource. |
| 412 | （Precondition Failed) The server does not meet one of the preconditions that the requester put on the request header fields. |
| 413 | （Payload Too Large) The request is larger than the server is willing or able to process. |
| 414 | （URI Too Long) The URI provided was too long for the server to process. |
| 415 | （Unsupported Media Type) The request entity has a media type which the server or resource does not support. |
| 416 | （Range Not Satisfiable) The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. |
| 417 | （Expectation Failed) The server cannot meet the requirements of the Expect request-header field. |
| 418 | （I'm a teapot) This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. |
| 419 | （Authentication Timeout (not in RFC 2616)) Not a part of the HTTP standard, 419 Authentication Timeout denotes that previously valid authentication has expired. It is used as an alternative to 401 Unauthorized in order to differentiate from otherwise authenticated clients being denied access to specific server resources. |
| 420 | （Method Failure (Spring Framework)) Not part of the HTTP standard, but defined by Spring in the HttpStatus class to be used when a method failed. This status code is deprecated by Spring. |
| 420 | （Enhance Your Calm (Twitter)) Not part of the HTTP standard, but returned by version 1 of the Twitter Search and Trends API when the client is rate-limited. Other services may wish to implement the 429 Too Many Requests response code instead. |
| 421 | The request was directed at a server that is not able to produce a response. (RFC 7540) |
| 422 | The request was well-formed but was unable to be followed due to semantic errors. (WebDAV; RFC 4918) |
| 423 | The resource that is being accessed is locked. (WebDAV; RFC 4918) |
| 424 | The request failed due to failure of a previous request (e.g., a PROPPATCH). (WebDAV; RFC 4918) |
| 425 | Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol" (RFC 3648). |
| 426 | The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field. (RFC 7231) |
| 428 | (Precondition Required) The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict." (RFC 6585) |
| 429 | （Too Many Requests) The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes. (RFC 6585) |
| 431 | （Request Header Fields Too Large) The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large. (RFC 6585) |
| 440 | （Login Timeout (Microsoft)) A Microsoft extension. Indicates that your session has expired. |
| 444 | （No Response (Nginx)) Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection (useful as a deterrent for malware). |
| 449 | （Retry With (Microsoft)) A Microsoft extension. The request should be retried after performing the appropriate action. |
| 450 | （Blocked by Windows Parental Controls (Microsoft)) A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage. |
| 451 | （Unavailable For Legal Reasons) Defined in the internet draft "A New HTTP Status Code for Legal Obstacles". Intended to be used when resource access is denied for legal reasons, e.g. censorship or government-mandated blocked access. A reference to the 1953 dystopian novel Fahrenheit 451, where books are outlawed. |
| 451 | （Redirect (Microsoft)) Used in Exchange ActiveSync if there either is a more efficient server to use or the server cannot access the users' mailbox. The client is supposed to re-run the HTTP Autodiscover operation to find a more appropriate server. |
| 494 | （Request Header Too Large (Nginx)) Nginx internal code similar to 431 but it was introduced earlier in version 0.9.4 (on January 21, 2011). |
| 495 | （Cert Error (Nginx)) Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection. |
| 496 | （No Cert (Nginx)) Nginx internal code used when client didn't provide certificate to distinguish it from 4XX in a log and an error page redirection. |
| 497 | （HTTP to HTTPS (Nginx)) Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection. |
| 498 | （Token expired/invalid (Esri)) Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token. |
| 499 | （Client Closed Request (Nginx)) Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back. |
| 499 | （Token required (Esri)) Returned by ArcGIS for Server. Code 499 indicates that a token is required (if no token was submitted). |
| 500 | （Internal Server Error) A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. |
| 501 | （Not Implemented) The server either does not recognize the request method, or it lacks the ability to fulfill the request. |
| 502 | （Bad Gateway) The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
| 503 | （Service Unavailable) The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. |
| 504 | （Gateway Timeout) The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. |
| 505 | The server does not support the HTTP protocol version used in the request. |
| 506 | Transparent content negotiation for the request results in a circular reference. (RFC 2295) |
| 507 | The server is unable to store the representation needed to complete the request. (WebDAV; RFC 4918) |
| 509 | This status code is not specified in any RFCs, but is used by some HTTP proxies to signal a bandwidth limit exceeding. |
| 510 | Further extensions to the request are required in order to fulfill it. (RFC 2774) |
| 508 | The server detected an infinite loop while processing the request. (WebDAV; RFC 5842) |
| 511 | The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network. (RFC 6585) |
| 520 | （Unknown Error) This status code is not specified in any RFCs, but is used by certain HTTP proxies to signal an error condition 520 Error. This is an unknown error. Essentially, it is a catch-all response for when the origin server returns something unexpected or that Cloudflare can't handle or interpret (protocol violation or empty response)". |
| 598 | （Network read timeout error (Unknown)) This status code is not specified in any RFCs, but is used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy. |
| 599 | （Network connect timeout error (Unknown)) This status code is not specified in any RFCs, but is used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy. |
© 2025 PCTOOLS Sitemap