List of 4xx Client Error codes

  • 400 Bad Request
    The request contains bad syntax or cannot be fulfilled.

  • 401 Unauthorized
    Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. See Basic access authentication and Digest access authentication.

  • 402 Payment Required
    The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.

  • 403 Forbidden
    The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

  • 404 Not Found
    The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

  • 405 Method Not Allowed
    A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

  • 406 Not Acceptable

  • 407 Proxy Authentication Required

  • 408 Request Timeout
    Client failed to continue the request

  • 409 Conflict

  • 410 Gone
    Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, in practice, a 404 Not Found is often issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes to prevent repeated requests.

  • 411 Length Required

  • 412 Precondition Failed

  • 413 Request Entity Too Large

  • 414 Request-URI Too Long

  • 415 Unsupported Media Type

  • 416 Requested Range Not Satisfiable
    The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).

  • 417 Expectation Failed

  • 418 I’m a teapot
    The HTCPCP server is a teapot. The responding entity MAY be short and stout. Defined by RFC 2324.

  • 422 Unprocessable Entity (WebDAV) (RFC 4918)
    The request was well-formed but was unable to be followed due to semantic errors.

  • 423 Locked (WebDAV) (RFC 4918)
    The resource that is being accessed is locked.

  • 424 Failed Dependency (WebDAV) (RFC 4918)
    The request failed due to failure of a previous request (e.g. a PROPPATCH).

  • 425 Unordered Collection
    Defined in drafts of WebDav Advanced Collections, but not present in “Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol” (RFC 3648).

  • 426 Upgrade Required (RFC 2817)
    The client should switch to TLS/1.0.

  • 428 Precondition Required (RFC 6585)
    The origin server requires the request to be conditional. Intended to prevent “the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.”

  • 449 Retry With
    A Microsoft extension. The request should be retried after doing the appropriate action.

  • 450 Blocked
    A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.