Server Error Reference Pages

400 = Bad RequestThe server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). 

401 = Unauthorized (RFC 7235)Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means "unauthenticated", i.e. the user does not have the necessary credentials. Note: Some sites issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website. 

402 = Payment RequiredReserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed for example by GNU Taler, but that has not yet happened, and this code is not usually used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.

403 = ForbiddenThe request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort. 

404 = Not FoundThe requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. 

405 = Method Not AllowedA request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource. 

406 = Not AcceptableThe requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation. 

407 = Proxy Authentication Required (RFC 7235)The client must first authenticate itself with the proxy. 

408 = Request TimeoutThe server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time." 

409 = ConflictIndicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates. 

410 = Gone - The server returns this response when the requested resource has been permanently removed. When a URL returns a 410 redirect, it means that the requested page does not exist anymore, and is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead. 

411 = Length RequiredThe request did not specify the length of its content, which is required by the requested resource. 

412 = Precondition Failed (RFC 7232)The server does not meet one of the preconditions that the requester put on the request. 

413 = Payload Too Large (RFC 7231)The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".

414 = URI Too Long (RFC 7231)The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously.

415 = Unsupported Media TypeThe request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. 

416 = Range Not Satisfiable (RFC 7233)The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously.

417 = Expectation FailedThe server cannot meet the requirements of the Expect request-header field. 

418 = I'm a teapot (RFC 2324, RFC 7168)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. The RFC specifies this code should be returned by teapots requested to brew coffee. This HTTP status is used as an Easter egg in some websites, including 

420 = { Unofficial } -A deprecated response used by the Spring Framework when a method has failed. Also - Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead. 

421 = Misdirected Request (RFC 7540)The request was directed at a server that is not able to produce a response (for example because of connection reuse).

422 = Unprocessable Entity (WebDAV; RFC 4918)The request was well-formed but was unable to be followed due to semantic errors. 

423 = Locked (WebDAV; RFC 4918)The resource that is being accessed is locked. 

424 = Failed Dependency (WebDAV; RFC 4918)The request failed because it depended on another request and that request failed (e.g., a PROPPATCH). 

426 = Upgrade RequiredThe client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field. 

428 = Precondition Required (RFC 6585)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." 

429 = Too Many Requests (RFC 6585)The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes. 

431 = Request Header Fields Too Large (RFC 6585)The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large. 

440 = Login Time-out The client's session has expired and must log in again. 

444 = No ResponseUsed internally to instruct the server to return no information to the client and close the connection immediately.

449 = Retry WithThe server cannot honour the request because the user has not provided the required information. 

450 = Blocked by Windows Parental Controls (Microsoft)The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.

451 = Unavailable For Legal Reasons (RFC 7725)A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource. The code 451 was chosen as a reference to the novel Fahrenheit 451 (see the Acknowledgements in the RFC). Also used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users' mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server. 

494 = Request header too largeClient sent too large request or too long header line. 

495 = SSL Certificate Error - An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate. 

496 = SSL Certificate Required - An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided. 

497 = HTTP Request Sent to HTTPS Port - An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests. 

498 = Invalid Token (Esri) Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.

499 = Token Required (Esri) - Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted. Also - Client Closed Request - Used when the client has closed the request before the server could send a response. 

World Wide Web Site Store

About Us

We offer totally risk–free Hosting & Business Solutions. We will give you a refund within the first month of your service subscription in case you are not satisfied with our service. We rarely, if ever, charge any set up fees either. We believe that getting another customer that puts his / her trust in us is much more important than receiving a one-time fee;  therefore you will never find any last minute, "hidden charges" in our bills to you.


Get product news, updates and resources.