HTTP Status codes // mostly useful for developers//

HTTP Status codes are :

Informational 1xx 

        It consist only of the status Line and optional headers ,& there are no required headers for the class of 

       status code.

        Servers must not be send a 1xx response to client 

100 Continue

          100 continue :  indicates the client should continue with its request.

        The server MUST send a final response after the request has been completed

101 Switching Protocols

      he server will switch protocols to those defined by the client response

Successful 2xx

      client's request was successfully received by the server.

201 Created

       The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. 

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 take place.

203 Non-Authoritative Information

 The returned maintain information 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. The set presented MAY be a subset or superset of the original version.

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.

Redirection 3xx

  This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.

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 (section 12) 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

           he requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. 

          

Found 302

           the requested data is available in another URL, then that time it goes 301 status code.

303 See Other

         he response to the request can be found under a different URI 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.

        

Not Modified 304

           have not permission to modify.

            If the client has requested GET type of request, then not permission to modify like signature and server responds with a 304 status code and does not send the document body to the client

305 Use Proxy

         he requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy.

306 (Unused)

             he 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.

307 Temporary Redirect

   The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.

Client Error 4xx

The 4xx class of status code is intended for cases in which the client seems to have erred

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

The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. 

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. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. 

404 Not Found

  Page not found..

405 Method Not Allowed

        The method specified 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 page or request not able to accept by the server from the client.

407 Proxy Authentication Required

      Validates the security mechanism applicable by the Proxy.

408 Request Timeout

         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

        he 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. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. 

411 Length Required

      The server refuses to accept the request without a defined Content- Length. 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.

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-URI Too Long

         The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. 

15 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 (section 14.35), 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 (see section 14.20) 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.

    

Server Error 5xx

          Server side error

500 Internal 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 Service Unavailable

             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.

504 Gateway Timeout

               The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.

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. 

________Thank     you________________________________________________________

------------------------Thank You------------------------------------------------------

               

     

     

      

    

    

  .