Glossary

200 - Is a browser code that signals that the website page was opened successfully.

301 - Is a browser code that signals a directory was requested instead of a file. The server substituted an index.htm file

302 - Is a browser code that signals a temporary redirection to another page/location.

403 - Is a browser code that means the browser understands what to do, but can't do it for some reason.

404 - Is a browser code that means the requested web address cannot be found.

500 - Is a browser code that means there was an error in displaying a webpage.

506 - Is a browser code that signals ASP is not enabled for the domain name.

507 - Is a browser code that means there is likely an error with the coding of a ASP page.

.net - Is a windows based platform for designing web pages. This is only supported on windows servers.

blackhole: - Emails addressed to non-existing accounts will automatically be deleted.

fail: - Emails addressed to non-existing accounts will automatically bounced back as undeliverable.

400 Bad Request - The Apache Web server allows site managers to override the standard error page that is served for specific errors by number. This error, 400 bad request, means that a request for a URL has been made but the server is not configured or capable of responding to it. This might be the case for URLs that are handed-off to a servlet engine where no default document or servlet is configured, or the HTTP request method is not implemented.

401 Unauthorized -Your IP address or the username/password you entered were not correct. Your request was denied as you have no permission to access the data.

402 Payment Required - The data is not accessible at the time. The owner of the space has not yet paid their service provider.

405 Method Not Allowed - Your IP address or the username/password you entered were not correct. Your request was denied as you have no permission to access the data.

OR The server was unable to serve the data that was requested.

406 Not Acceptable - The document that has been requested either no longer exists, or has never existed on the server.

407 Proxy Authentication Required - The browser has not been authenticated on the required proxy server to access the data. This error is probably most commonly returned by content filters/parental controls.

408 Request Timeout - The browser has not been authenticated on the required proxy server to access the data. This error is probably most commonly returned by content filters/parental controls.

409 Conflict - Too many requests for the same file at one time.

OR There is a conflict with an established software rule. (ie: you are trying to copy over a file with an older version, or you do not have permissions to delete a file)

OR This could be caused by a DNS issue.

410 Gone - This is like a 404 error in that the document requested is not on the server, however this differs in that the server 'knows' that the file used to be there and 'believes' that the file may be back, so it returns 410 rather 404.

411- Length Required: Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) should include a 'Content-Length' specification. This is typically used only for HTTP methods that result in the placement of data on the Web server, not the retrieval of data from it.

412- Precondition Failed: Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) included a 'Precondition' specification which the server detected was not met.

413- Request Entity Too Large: Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was simply too large i.e. too many bytes. What constitutes 'too many bytes' depends partly upon the operation being attempted. For example a request to upload a very large file (via the HTTP PUT method) may encounter a ceiling on upload file size set by the Web server.

414- Request- URI Too Long: Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) contains a URL that is simply too large i.e. too many bytes.

Typically Web servers set fairly generous limits on length for genuine URLs e.g. up to 2048 or 4096 characters. If your URL is particularly long, you can usually try shorter variations to see roughly where the limit is. If your long URL is indeed valid, then the Web server may need to be reconfigured to allow your URLs through. Understand that Web servers have to set some reasonable limit here, because they have to deal with badly programmed clients trying to give them huge garbage URLs.

415- Unsupported Media Type: Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) identifies a URL resource whose actual media type 1) does not agree with the media type specified on the request or 2) is incompatible with the current data for the resource or 3) is incompatible with the HTTP method specified on the request.Detecting exactly what is causing this problem can be difficult, because there a number of possible reasons. Often the request involves transfer of data from the client to the Web server (e.g. a file upload via the PUT method), in which case you need to confirm with your ISP which media types are acceptable for upload.

501- Not implemented: Your Web server does not understand or does not support the HTTP method it finds in the HTTP data stream sent to it by the client (e.g. a Web browser or our CheckUpDown robot).

502- Bad Gateway: A server (not necessarily a Web server) is acting as a gateway or proxy to fulfill the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfill the request.This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.

503- Service Unavailable: Your Web server is currently unable to handle the HTTP 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. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.

504- Gateway Timeout: A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.This usually means that the upstream server is down (no response to the gateway/proxy rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

505- HTTP Version Not Supported: Your Web server does not support, or refuses to support, the HTTP protocol version specified by the client

(e.g. your Web browser or our CheckUpDown robot) in the HTTP request data stream sent to the server.The HTTP protocol has various versions identified as major.minor e.g. version 0.9, 1.0 or 1.1. Your server is indicating that it is unable or unwilling to complete the request using the major version provided by the client - other than with this error message.Assuming that your request identifies a valid major.minor version number (the request is not fundamentally corrupt), then this error should mostly only occur if you are trying to use version 1.0 or 1.1, but your Web server only supports the older 0.9 version.