HTML Errors

          Status-Code    = "100"   ; Continue
                         | "101"   ; Switching Protocols
                         | "200"   ; OK
                         | "201"   ; Created
                         | "202"   ; Accepted
                         | "203"   ; Non-Authoritative Information
                         | "204"   ; No Content
                         | "205"   ; Reset Content
                         | "206"   ; Partial Content
                         | "300"   ; Multiple Choices
                         | "301"   ; Moved Permanently
                         | "302"   ; Moved Temporarily
                         | "303"   ; See Other
                         | "304"   ; Not Modified
                         | "305"   ; Use Proxy
                         | "400"   ; Bad Request
                         | "401"   ; Unauthorized
                         | "402"   ; Payment Required
                         | "403"   ; Forbidden
                         | "404"   ; Not Found
                         | "405"   ; Method Not Allowed
                         | "406"   ; Not Acceptable
                         | "407"   ; Proxy Authentication Required
                         | "408"   ; Request Time-out
                         | "409"   ; Conflict
                         | "410"   ; Gone
                         | "411"   ; Length Required
                         | "412"   ; Precondition Failed
                         | "413"   ; Request Entity Too Large
                         | "414"   ; Request-URI Too Large
                         | "415"   ; Unsupported Media Type
                         | "500"   ; Internal Server Error
                         | "501"   ; Not Implemented
                         | "502"   ; Bad Gateway
                         | "503"   ; Service Unavailable
                         | "504"   ; Gateway Time-out
                         | "505"   ; HTTP Version not supported
                        
         
 Informational 1xx   To The Top

This class of status code indicates a provisional response, consisting only of the 
Status-Line and optional headers, and is terminated by an empty line. HTTP/1.0 does 
not define any 1xx status codes and they are not a valid response to a HTTP/1.0 request. 
However, they may be useful for experimental applications which are outside the scope of 
this specification. 




 Successful 2xx   To The Top
This class of status code indicates that the client's request was successfully received, 
understood, and accepted. 


200 OK   To The Top
The request has succeeded. The information returned with the response is dependent on the 
method used in the request, as follows: 

GET
an entity corresponding to the requested resource is sent in the response; 

HEAD
the response must only contain the header information and no Entity-Body; 

POST
an entity describing or containing the result of the action. 

201 Created   To The Top
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. 
The origin server should create the resource before using this Status-Code. If the action 
cannot be carried out immediately, the server must include in the response body a 
description of when the resource will be available; otherwise, the server should respond 
with 202 (accepted). 

Of the methods defined by this specification, only POST can create a resource. 


202 Accepted   To The Top
The request has been accepted for processing, but the processing has not been completed. 
The request may or may not eventually be acted upon, as it may be disallowed when processing
 actually takes place. There is no facility for re-sending a status code from an 
asynchronous operation such as this. 

The 202 response is intentionally non-committal. Its purpose is to allow a server to accept 
a request for some other process (perhaps a batch-oriented process that is only run once
per day) without requiring that the user agent's connection to the server persist until the 
process is completed. The entity returned with this response should include an indication 
of the request's current status and either a pointer to a status monitor or some estimate
of when the user can expect the request to be fulfilled. 

204 No Content   To The Top
The server has fulfilled the request but there is no new information to send back. If the 
client is a user agent, it should not change its document view from that which caused the 
request to be generated. This response is primarily intended to allow input for scripts or
other actions to take place without causing a change to the user agent's active document 
view. The response may include new metainformation in the form of entity headers, which 
should apply to the document currently in the user agent's active view. 


 Redirection 3xx   To The Top

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 subsequent 
request is GET or HEAD. A user agent should never automatically redirect a request more 
than 5 times, since such redirections usually indicate an infinite loop. 


300 Multiple Choices   To The Top
This response code is not directly used by HTTP/1.0 applications, but serves as the default 
or interpreting the 3xx class of responses. 
The requested resource is available at one or more locations. Unless it was a HEAD request,
 the response should include an entity containing a list of resource characteristics and 
locations from which the user or user agent can choose the one most appropriate. If the 
server has a preferred choice, it should include the URL in a Location field; user agents 
may use this field value for automatic redirection. 


301 Moved Permanently   To The Top
The requested resource has been assigned a new permanent URL and any future references to 
this resource should be done using that URL. Clients with link editing capabilities should 
automatically relink references to the Request-URI to the new reference returned by the 
server, where possible. 

The new URL must be given by the Location field in the response. Unless it was a HEAD 
request, the Entity-Body of the response should contain a short note with a hyperlink to 
the new URL. 

If the 301 status code is received in response to a request using the POST method, the 
user agent must not automatically redirect the request unless it can be confirmed by the 
user, since this might change the conditions under which the request was issued. 


Note: When automatically redirecting a POST request after receiving a 301 status code,
some existing user agents will erroneously change it into a GET request. 

302 Moved Temporarily   To The Top
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-URI for future 
requests. 

The URL must be given by the Location field in the response. Unless it was a HEAD request, 
the Entity-Body of the response should contain a short note with a hyperlink to the new 
URI(s). 

If the 302 status code is received in response to a request using the POST method, the user 
agent must not automatically redirect the request unless it can be confirmed by the user, 
since this might change the conditions under which the request was issued. 


Note: When automatically redirecting a POST request after receiving a 302 status code, some 
existing user agents will erroneously change it into a GET request. 

304 Not Modified   To The Top
If the client has performed a conditional GET request and access is allowed, but the 
document has not been modified since the date and time specified in the If-Modified-Since 
field, the server must respond with this status code and not send an Entity-Body to the 
client. Header fields contained in the response should only include information which is 
relevant to cache managers or which may have changed independently of the entity's 
Last-Modified date. Examples of relevant header fields include: Date, Server, and Expires. 
A cache should update its cached entity to reflect any new field values given in the 304 
response. 


Client Error 4xx   To The Top

The 4xx class of status code is intended for cases in which the client seems to have erred. 
If the client has not completed the request when a 4xx code is received, it should immediately 
cease sending data to the server. 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. These status codes are applicable to any request method. 


Note: If the client is sending data, server implementations on TCP should be careful to 
ensure that the client acknowledges receipt of the packet(s) containing the response prior 
to closing the input connection. If the client continues sending data to the server after 
the close, the server's controller will send a reset packet to the client, which may erase 
the client's unacknowledged input buffers before they can be read and interpreted by the 
HTTP application. 

400 Bad Request   To The Top
The request could not be understood by the server due to malformed syntax. The client 
should not repeat the request without modifications. 


401 Unauthorized   To The Top
The request requires user authentication. The response must include a WWW-Authenticate 
header field (Section 10.16) containing a challenge applicable to the requested resource. 
The client may repeat the request with a suitable Authorization header field. If the 
request already included Authorization credentials, then the 401 response indicates that 
authorization has been refused for those credentials. If the 401 response contains the 
same challenge as the prior response, and the user agent has already attempted authentication 
at least once, then the user should be presented the entity that was given in the response, 
since that entity may include relevant diagnostic information. HTTP access authentication is explained in Section 11. 


403 Forbidden      To The Top
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 body. 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. 


404 Not Found   To The Top
The server has not found anything matching the Request-URI. No indication is given of 
whether the condition is temporary or permanent. If the server does not wish to make this 
information available to the client, the status code 403 (forbidden) can be used instead. 


Server Error 5xx   To The Top

Response status codes beginning with the digit "5" indicate cases in which the server is aware 
that it has erred or is incapable of performing the request. If the client has not completed 
the request when a 5xx code is received, it should immediately cease sending data to the server. 
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. 
These response codes are applicable to any request method and there are no required header 
fields. 


500 Internal Server Error   To The Top
The server encountered an unexpected condition which prevented it from fulfilling the request. 


501 Not Implemented   To The Top
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   To The Top
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   To The Top
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.