HTTP Error Codes:
Error codes will help you identify the reason why your website is reported 'down' by Site24x7. Below table gives a fair idea about different HTTP error codes, corresponding reason and World Wide Web Consortium definitions for each error code.
|
Error Code |
Reason |
Description |
| 613 |
Response Timeout |
The server, did not respond to the request for more than 2 minutes. |
| 614 |
Too many Re-directions |
The request got redirected for more than 10 times. |
| 615 |
SSL Connection Error | SSL connection to the server failed. |
| 400 | Bad File Request |
Syntax used in the request (URL) is incorrect |
| 401 |
Unauthorized | Authorization required. Happens usually when a wrong password is entered. |
| 403 | Forbidden/Access Denied |
Server denies a particular request usually due to restricted access permissions set up on its directories. |
| 404 | Page/File Not Found |
Server cannot find the requested URL. |
| 405 |
Method Not Allowed | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. |
| 406 |
Not Acceptable | Server is unable to generate a response which can be accepted by the requester. |
| 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 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 | The request could not be completed due to a conflict with the current state of the resource. |
| 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. |
| 414 |
Request URL Too Long | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. |
| 500 |
Internal Error |
The server encountered an unexpected condition which prevented it from fulfilling the request. |
| 501 | No Server |
The server does not support the functionality required to fulfill the request. |
| 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. |
| 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. |
Error codes reference: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html