404 Not Found
Unfortunately, we were unable to find any page matching the requested
URL
.
The most common cause is an invalid web address.
You might be interested in learning about the other 4xx class class of status code which are intended for cases in which the client seems to have made some sort of request error (adapted from RFC2616):
- 400 Bad Request: The request could not be understood by the
server
due to malformed syntax.
- 401 Unauthorized: The request requires user authentication.
- 402 Payment Required: This code is reserved for future use.
- 403 Forbidden: The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the server does not wish to make this information available to the
client
, the status code 404 (Not Found) can be used instead.
- 404 Not Found: The server has not found anything matching the Request-
URI
. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. 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.
- 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: The resource identified by the request cannot be sent in a format acceptable to the user agent. A
user agent
SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.
- 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.
- 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. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.
- 411 Length Required: The server refuses to accept the request without a defined Content-Length.
- 412 Precondition Failed: The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
- 413 Request Entity Too Large: The server is refusing to process a request because the request is larger than the server is willing or able to process. Common cause is trying to upload a file that is larger than permitted.
- 414 Request-URI Too Long: The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
- 415 Unsupported Media Type: The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
- 416 Requested Range Not Satisfiable: A server SHOULD return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource.
- 417 Expectation Failed: The expectation given in an Expect request-header field could not be met by this server.