On the left side of the Viewable Pages List is a series of icons for each page. These icons identify information, including the StatusCode, about each page.
For definitions of status codes in the W3C standard, visit http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.
3xx Redirect pages
The W3C standards define a number of redirect StatusCodes, the 300 series. This class of status code indicates that further action must be taken by the user agent to fulfill the request.
Many StatusCodes specify a new location for the URI. This new location is part of the response and is called the location field.
Descriptions for 3xx errors follow:
| Status code | Description |
|---|---|
301 Moved Permanently |
The requested resource is signed a new permanent URI. Any future references to this resource must use returned URIs. The new permanent URI must be provided in the Location field in the response. |
302 Found |
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client must continue to use the Request-URI for future requests. |
303 See Other |
The response to the request can be found under a different URI and must be retrieved by using a GET method on that resource. |
304 Not Modified |
If the client completes a conditional GET request and access is allowed yet the document is not been modified, the server must respond with this status code. The 304 response must not contain a message-body. It is always terminated by the first empty line after the header fields. The 304 Status Code has its own special icon. |
305 Use Proxy |
The requested resource must be accessed through the proxy that is given by the Location field. The Location field gives the URI of the proxy. |
4xx errors
The 4xx class of StatusCode is intended for cases in which the client seems to have erred. The server must include an explanation of the error situation and indication of whether it is a temporary or permanent condition. These status codes are applicable to any request method.
In addition to these codes, the W3C standard defines a number of other 4xx codes which are not common.
| Status code | Description |
|---|---|
400 Bad Request |
The request could not be understood by the server because of malformed syntax. |
401 Unauthorized |
The request requires user authentication. The response must include a WWW-Authenticate header field that contains a challenge applicable to the requested resource. The client can repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization is refused for those credentials. |
403 Forbidden |
The server understood the request but is refusing to fulfill it. |
404 Not Found |
The server has not found anything that matches the Request-URI. No indication is given of whether the condition is temporary or permanent. This status code is commonly used when the server does not want to reveal exactly why the request is refused, or when no other response is applicable. |
405 Method Not Allowed |
The method that is specified in the Request-Line is not allowed for the resource that is identified by the Request-URI. The response must include an Allow header that contains a list of valid methods for the requested resource. |
406 Not Acceptable |
The resource that is identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers that are sent in the request. |
407 Proxy Authentication Required |
This code is similar to 401 (Unauthorized), but it indicates that the client must first authenticate itself with the proxy. The proxy must return a Proxy-Authenticate header field that contains a challenge applicable to the proxy for the requested resource. The client can repeat the request with a suitable Proxy-Authenticate header field. |
408 Request Timeout |
The client did not produce a request within the time that the server was prepared to wait. The client can repeat the request without modifications at any later time. |
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. |
5xx errors
Response Status Codes that begin with the digit 5 indicate cases in which the
server is aware that it has erred or is incapable of completing the request. These response codes
are applicable to any request method. The same icon that is displayed in the above figure is used
for 5xx errors.
Descriptions for 5xx errors follow:
| Status code | Description |
|---|---|
500 Internal Server Error |
The server encountered an unexpected condition that prevented it from fulfilling the request. |
501 Not Implemented |
The server does not support the functionality that is required to fulfill the request. |
502 Bad Gateway |
While it acts as a gateway or proxy, the server received an invalid response from the upstream server it accessed while it attempts to fulfill the request. |
503 Service Unavailable |
The server is unable to handle the request because of temporary overloading or maintenance of the server. This error implies that the temporary condition will be alleviated after some delay. The existence of the 503 status code does not imply that a server must use it when it becomes overloaded. Some servers can refuse the connection. |
504 Gateway Timeout |
While it acts as a gateway or proxy, the server did not receive a timely response from the upstream server specified by the URI. |
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. |