HTTP Error Codes

Code Number

Error Message

Meaning
100 Continue The client should continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client should continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server must send a final response after the request has been completed.
101 Switching Protocols The server understands and is willing to comply with the client’s request, via the Upgrade message header field), for a change in the application protocol being used on this connection. 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.
200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request.
201 Created The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URL(s) returned in the entity of the response, with the most specific URL for the resource given by a Location header field. The response should include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate.
202 Accepted The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.
203 Non-Authoritative Information The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.
204 No Content The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response may include new or updated metainformation in the form of entity-headers, which if present should be associated with the requested variant.
205 Reset Content The server has fulfilled the request and the user agent should reset the document view which caused the request to be sent. 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 the user can easily initiate another input action.
206 Partial Content The server has fulfilled the partial GET request for the resource.
300 Multiple Choices The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
301 Moved Permanently The requested resource has been assigned a new permanent URL and any future references to this resource should use one of the returned URLs.
302 Moved Temporarily The requested resource resides temporarily under a different URL. Since the redirection might be altered on occasion, the client should continue to use the Request-URL for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
303 See Other The response to the request can be found under a different URL and should be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URL is not a substitute reference for the originally requested resource.
304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server should respond with this status code.
305 Use Proxy The requested resource MUST be accessed through the proxy given by the Location field.
307 Temporary Redirect The requested resource resides temporarily under a different URL. Since the redirection may be altered on occasion, the client should continue to use the Request-URL for future requests.
400 Bad Request The request could not be understood by the server due to malformed syntax.
401 Unauthorized The request requires user authentication, typically a Username/Password credential pair. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials.
402 Payment Required This code is reserved for future use.
403 Forbidden The server understood the request, but is refusing to fulfill it. Authorization will not help and the request should NOT be repeated.
404 Not Found The server has not found anything matching the Request-URL. No indication is given of whether the condition is temporary or permanent. 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. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
405 Method Not Allowed The method specified in the Request-Line is not allowed for the resource identified by the Request-URL.
406 Not Acceptable The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
407 Proxy Authentication Required This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
408 Request Time-Out 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 Conflict The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request.
410 Gone The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.
411 Length Required The server refuses to accept the request without a defined Content-Length.
412 Precondition Failed The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
413 Request Entity Too Large The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.
414 Request-URL Too Large The server is refusing to service the request because the Request-URL is longer than the server is willing to interpret. 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 a URL “black hole” of redirection (e.g., a redirected URL prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URL.
415 Unsupported Media Type The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
416 Requested Range Not Satisfiable A server should return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field.
417 Expectation Failed The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
500 Server Error The server encountered an unexpected condition which prevented it from fulfilling the request.
501 Not Implemented The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
503 Out of Resources The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
504 Gateway Time-Out The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URL (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request. Note: Some deployed proxies are known to return 400 or 500 when DNS lookups time out.
505 HTTP Version not supported The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.

Sign My Guestbook Guestbook by GuestWorld View My Guestbook