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 payed their service provider.
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.
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.
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.
