Rainbows Puppies & Sunshine
Our Company Gizmos Tools Admin

   

HTTP Status Codes

Each hundred numbers of HTTP status codes designate a type of HTTP status. Listed below are descriptions of each grouping. Further down are specific HTTP status codes along with their exact descriptions. You can click on any of the below groupings to be taken to all the specific HTTP status codes within that category.

Informational
100's
Succesful
200's
Redirection
300's
Client Error
400's
Server Error
500's

You can use the below form to reload this page to a specific HTTP status code or submit the word 'All' to view every one.

Informational Status Codes

  100 Continue
  101 Switching Protocols

Succesful Status Codes

  200 OK Action complete successfully
  201 Created Success following a POST command
  202 Accepted The request has been accepted for processing, but the processing has not been completed.
  203 Partial Information Response to a GET command, indicates that the returned meta information is from a private overlaid web.
  204 No Content Server has received the request but there is no information to send back.
  205 Reset Content Request fulfilled and user agent should reset document that caused the request. Used to allow user input followed by reseting the input form. The response MUST NOT include an entity.
  206 Partial Content The requested file was partially sent. Usually caused by stopping or refreshing a web page.

Redirection Status Codes

  300 Multiple Choices Requested resource corresponds to a set of representations, each with its own location. Negotiation information is provided so that the representation can be selected and redirect appropriately.
  301 Moved Permanently Requested a directory instead of a file. The web server substituted the index.htm file.
  302 Found The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
  303 See Other The response to the request is at a different URI and should be retrieved there using a GET method. This allows the output of a POST-activated script to redirect the user agent to a selected resource.
  304 Not Modified The cached version of the requested file is the same as the file to be sent.
  305 Use Proxy The requested resource must be accessed through the proxy given in the Location field. The recipient should repeat this request via the proxy. This response must only be generated by origin servers.
  306 Unused Reserved for future use
  307 Temporary redirect The requested resource resides temporarily under a different URI.

Client Error Status Codes

  400 Bad Request The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
  401 Unauthorized User fail to provide a valid user name / password required for access to file / directory.
  402 Payment Required 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-URI. No indication is given of whether the condition is temporary or permanent.
  405 Method Not Allowed The method in the Request-Line is not allowed for the resource identified by the Request-URI. The response must include an Allow header containing a list of valid methods for the requested resource.
  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.
  410 Gone The requested resource is no longer available at the server and no forwarding address is known.
  411 Length Required The server refuses to accept the request without a defined Content-Length of the message-body. The client may repeat the request if it adds it.
  412 Precondition Failed A condition in the header field data passed by the client evaluated false on the server. This lets the client prevent the requested method from being applied to a resource other than the one intended.
  413 Request Entity Too Large The server refused to process the request because the request entity too large. The server may close the connection to prevent the client from continuing the request.
  414 Request-URI Too Large The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
  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 Unsatisfiable Request Range A server SHOULD return a response with this status code if a request included a Range request-header field
  417 Expectation Failed The server could not meet the expectation in an Expect request-header field. If the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.

Server Error Status Codes

  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 facility required.
  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 cannot process the request due to a system overload. This (should) be a temporary condition.
  504 Gateway Time-Out The service did not respond within the time frame that the gateway was willing to wait.
  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.

The functionality of this section or any other section of this site can be customized to your needs. Contact Us and let us know how we can help.

Our Company Gizmos Tools Admin
©2007-2017 Rainbows Puppies & Sunshine, LLC.