HTTP Status Codes

Information about all HTTP status codes, their meaning, and any related restrictions. Use the filters to narrow down your search.

100 - Informational

An error occurred on the server and it is unable to complete the request. Information about the error should be returned and displayed unless a HEAD request was performed.

  • Continue

    Indicates that request headers have been received and the client should send the request body (if any). This requires the client to send an Expect: 100-continue header in the request.

    If an error code is returned then the client should not send the request body.

    If the server is unable to support the Expect header then a 417 will be returned.

  • Switching Protocols

    The client has requested to switch protocols and the server has agreed.

  • Processing

    Indicates the server is processing the request but has not yet finished.

  • Early Hints

    Return response headers before final HTTP response.

  • Checkpoint

    Used in resumable requests.

200 - Success

An error occurred on the server and it is unable to complete the request. Information about the error should be returned and displayed unless a HEAD request was performed.

  • OK

    Standard response indicating a successful action. For GET requests this will be the resource, and for POST it will be the result of the action.

  • Created

    The request was successful and a new resource was created.

  • Accepted

    The request was accepted but has not yet completed.

  • Non Authoritative Information

    The server is a proxy that returned a 200 from the origin and is returning a modified version of the response.

  • No Content

    The server has processed the request and no content is returned.

  • Reset Content

    The server has processed the request and no content is returned, but asks that the client reset its view.

  • Partial Content

    Only part of the resource is returned. This is caused by a range request. This is typically used to resume or split a download.

  • Multi-Status

    Multiple response codes are included as part of an XML document.

  • Already Reported

    A WebDAV binding has been enumerated in a previous 207 and are not included here again.

  • This Is Fine

    A catch-all error to allow responses through Apache when ProxyErrorOverride is enabled. When enabled any 4xx or 5xx is discarded and this generic response is returned.

  • IM Used

    The request has been fulfilled.

300 - Redirect

An error occurred on the server and it is unable to complete the request. Information about the error should be returned and displayed unless a HEAD request was performed.

  • Multiple Choices

    There are multiple versions of the resource from which the client can choose.

  • Moved Permanently

    This and all future requests should be directed to the given URI. The request method can change.

  • Moved Temporarily

    The resource has temporarily been moved to another location. This is superseded by 303 and 307.

  • See Other

    The resource is found at another location. For POST, PUT, and DELETE requests the client should assume the data has been received.

  • Not Modified

    The resource has not been modified since the time specified by the if-modified-since or if-none-match headers and there is no need to re-download it.

  • Use Proxy

    The resource is only available through the proxy specified in the response. Mozilla Firefox and Internet Explorer do not follow this rule.

  • Switch Proxy

    Switch to the specified proxy. This is no longer used.

  • Temporary Redirect

    The request should use the URI specified, but subsequent requests should continue using the original URI. The request method should not change.

  • Permanent Redirect

    This and all future requests should be directed to the given URI. This is similar to 301 but the request method cannot change.

400 - Client Error

An error situation occurred which seems to be caused by the client. Information about the error should be returned and displayed unless a HEAD request was performed.

500 - Server Error

An error occurred on the server and it is unable to complete the request. Information about the error should be returned and displayed unless a HEAD request was performed.

References: Wikipedia, Mozilla.