Home > Error Code > Standard Error Codes

Standard Error Codes


This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that Wikipedia The URI provided was too long for the server to process. 415 Unsupported Media Type The server is refusing to service the request because the entity of the request is Retrieved 16 October 2015. ^ "RFC7231 on code 400". Resend the request to the same path, but without the /download prefix. have a peek here

Wikipedia The response to the request can be found under another URI using a GET method. Retrieved October 24, 2009. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4". The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server. unsupportedOutputFormat The alt parameter value specifies an output format that is not supported for this service.

Http Status Code 400

The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into

Resubmitting elsewhere without any key change when a paper is rejected Unable to complete a task at work. Reply ↓ Tyler March 29, 2013 at 9:22 pm Good suggestion about a 501. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. Http Response Example The actual response will depend on the request method used.

The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. Http Status Codes Cheat Sheet Wikipedia The server does not support the HTTP protocol version used in the request. 506 Variant Also Negotiates (Experimental) The 506 status code indicates that the server has an internal configuration Retrieved 16 October 2015. ^ "RFC2616 on status 414". April 2015.

In some situations, letting the Web server reply with a 404 will send the generic "Not Found" HTML page back to the caller which doesn't make sense if there's not a Error Code List There must be no body on the response. 305 Use Proxy The requested resource MUST be accessed through the proxy given by the Location field. Retrieved January 8, 2015. ^ "401". Please use the Google Developer Console (https://developers.google.com/console) to create a project for your application.

Http Status Codes Cheat Sheet

However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. Check the value of the Authorization HTTP request header. Http Status Code 400 https://tools.ietf.org/html/rfc2774. Http Code 403 The server MUST send a final response after the request has been completed.

sec.10.2.1. navigate here The Google Static Maps API returns a message as text in clear English if I make a wrong call. If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. Why is bench pressing your bodyweight harder than doing a pushup? Http Code 302

If you aren’t registered yet, please register now for free or join as a Premier Member. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. Microsoft. 2009. Check This Out User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable.

Google Maps API) solve this? Error Code 500 Many APIs also define their own domains, which identify API-specific errors that are not in the global domain. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.

It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes.

This code indicates that the server has received and is processing the request, but no response is available yet.[6] This prevents the client from timing out and assuming the request was share|improve this answer answered May 15 '13 at 10:05 Stuart 50848 add a comment| up vote 1 down vote There's no standard, and why should there be? Wikipedia A generic error message, given when no more specific message is suitable. Http 422 The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.

Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. In both cases, the protocol definition explicitly says that servers "SHOULD include an entity containing an explanation of the error situation", so it's a good practice to do it. The server MUST send a final response after the request has been completed. this contact form So, for example, submitting a form to a permanently redirected resource may continue smoothly.[30] 4xx Client Error[edit] 404 error on German Wikipedia The 4xx class of status code is intended for

These status codes are applicable to any request method. quotaExceeded The requested operation requires more resources than the quota allows. Wikipedia No longer used. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. 10.4.5 404 Not Found The server has

However, these risks are not unique to the 511 status code; in other words, a captive portal that is not using this status code introduces the same issues. March 3, 2003. A response received with a status code of 226 MAY be stored by a cache and used in reply to a subsequent request, subject to the HTTP expiration mechanism and any The server should send back all the information necessary for the client to issue an extended request.

If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. This response is cacheable unless indicated otherwise. Intended for use with rate limiting schemes. 431 Request Header Fields Too Large The 431 status code indicates that the server is unwilling to process the request because its header fields This response is only cacheable if indicated by a Cache-Control or Expires header field.

June 1999. The RFC specifies this code should be returned by teapots requested to brew coffee.[49] This HTTP status is used as an Easter egg in some websites, including Google.com.[50] 421 Misdirected Request Usually this implies future availability (e.g., a new feature of a web-service API).[citation needed] 502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes

RFC 2518. Retrieved 16 October 2015. ^ ikitommi; Deraen. "metosin/ring-http-response". DNS) it needed to access in attempting to complete the request. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client. 10.3.4 303 See Other The

If the 510 response contains information about extensions that were not present in the initial request then the client MAY repeat the request if it has reason to believe it can