HTTP Status Codes

Result

Status code

404 Not Found

Meaning

• Class 4xx: Client error
• There is nothing at this address. Common causes are typos in the URL, deleted pages and broken links.

Codes at a glance

Code	Name	Meaning
400	Bad Request	The server cannot understand the request, for example because of bad syntax, invalid parameters or damaged cookies.
401	Unauthorized	Valid authentication is missing. The client must identify itself, for example with a username and password or a token.
402	Payment Required	Reserved for payment. Some services use it when an account or plan is unpaid.
403	Forbidden	The server understands the request but refuses access. Logging in does not help, the permissions are missing.
404	Not Found	There is nothing at this address. Common causes are typos in the URL, deleted pages and broken links.
405	Method Not Allowed	The method (such as POST) is not allowed for this address. The Allow header lists the permitted methods.
406	Not Acceptable	The server cannot produce a response in any of the requested formats or languages.
408	Request Timeout	The server waited too long for the complete request and closed the connection.
409	Conflict	The request conflicts with the current state of the resource, for example with simultaneous edits.
410	Gone	The page is gone for good and will not come back. Search engines usually drop it faster than with 404.
411	Length Required	The server requires the content length (Content-Length) to be stated in the request.
412	Precondition Failed	A condition in the request headers, such as If-Match, was not met, so nothing was changed.
413	Content Too Large	The request content is larger than the server allows, for example an upload that is too big.
414	URI Too Long	The address is longer than the server can process. Often there are too many parameters in the URL.
415	Unsupported Media Type	The server does not know the format of the content sent, for example because of a wrong Content-Type.
416	Range Not Satisfiable	The requested range lies outside the file, for example with a wrongly resumed download.
418	I’m a teapot	An April Fools’ joke from RFC 2324: a teapot cannot brew coffee. Some servers use the code for fun.
422	Unprocessable Content	The request is formally correct but cannot be processed, for example because of invalid field values in an API.
429	Too Many Requests	Too many requests in a short time. The Retry-After header often tells when it works again.
431	Request Header Fields Too Large	The request header fields are too large, often because of too many or too big cookies.
451	Unavailable For Legal Reasons	Access is blocked for legal reasons, for example by an order from an authority.