This page provides a comprehensive overview of HTTP status codes, categorized by their response class. Understanding these codes is crucial for diagnosing and debugging network communication issues.
The request was received, continuing process.
Description: The server has received the request headers and the client should proceed with sending the request body.
RFC: RFC 7231
Description: The server understands and will comply with the client's request to switch protocols.
RFC: RFC 7231
Description: The server has received and is processing the request, but no response is available yet.
RFC: RFC 2518
The action was successfully received, understood, and accepted.
Description: The request has succeeded.
RFC: RFC 7231
Description: The request has been fulfilled and resulted in a new resource being created.
RFC: RFC 7231
Description: The request has been accepted for processing, but the processing has not been completed.
RFC: RFC 7231
Description: The server successfully processed the request and is not returning any content.
RFC: RFC 7231
Further action needs to be taken by the user agent in order to complete the request.
Description: The requested resource has been permanently moved to a new URL. The client should use the new URL for future requests.
RFC: RFC 7231
Description: The requested resource is temporarily located at a different URL. The client should try again at the original URL.
RFC: RFC 7231
Description: The client has performed a conditional request for a resource and the resource has not been modified.
RFC: RFC 7232
The request contains bad syntax or cannot be fulfilled.
Description: The server cannot or will not process the request due to something that is perceived to be a client error.
RFC: RFC 7231
Description: The request requires user authentication. The client must authenticate itself to get the requested response.
RFC: RFC 7235
Description: The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested information.
RFC: RFC 7231
Description: The server cannot find the requested resource. This error is common and indicates that the URL entered is incorrect or the resource has been moved or deleted.
RFC: RFC 7231
Description: The request method is known by the server but is not supported by the target resource.
RFC: RFC 7231
Description: The request could not be completed because of a conflict with the current state of the target resource.
RFC: RFC 7231
Description: Indicates that the resource requested is no longer available and will not be available again. This should be used when the resource has been deliberately removed and the owner wants to make sure that the resource is not accessible by forwarding the client to an alternative resource.
RFC: RFC 7231
Description: The user has sent too many requests in a given amount of time. This is often used as part of a rate-limiting strategy.
RFC: RFC 6585
The server failed to fulfill an apparently valid request.
Description: A generic error message, given when no more specific message is suitable. This indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
RFC: RFC 7231
Description: The server does not support the functionality required to fulfill the request.
RFC: RFC 7231
Description: The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
RFC: RFC 7231
Description: The server is currently unable to handle the request due to temporary overloading or maintenance of the server.
RFC: RFC 7231
Description: The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
RFC: RFC 7231