Complete reference for HTTP status codes
The server has received the request headers, and the client should proceed to send the request body.
The requester has asked the server to switch protocols.
The server has received and is processing the request, but no response is available yet.
The request succeeded. The meaning depends on the HTTP method used.
The request succeeded, and a new resource was created as a result.
The request has been received but not yet acted upon.
There is no content to send for this request, but the headers may be useful.
The server is delivering only part of the resource due to a range header sent by the client.
The request has more than one possible response.
The URL of the requested resource has been changed permanently.
The URI of requested resource has been changed temporarily.
The response has not been modified, so the client can use the cached version.
The server sends this response to direct the client to get the requested resource at another URI with the same method.
The resource is now permanently located at another URI, specified by the Location header.
The server cannot process the request due to client error (e.g., malformed request syntax).
Authentication is required and has failed or has not been provided.
The client does not have access rights to the content.
The server cannot find the requested resource.
The request method is known by the server but is not supported by the target resource.
The server timed out waiting for the request.
The request conflicts with the current state of the server.
The requested content has been permanently deleted from server.
Request entity is larger than limits defined by server.
The URI requested by the client is longer than the server is willing to interpret.
The media format of the requested data is not supported by the server.
The user has sent too many requests in a given amount of time ("rate limiting").
The server has encountered a situation it does not know how to handle.
The request method is not supported by the server and cannot be handled.
The server, while working as a gateway, received an invalid response.
The server is not ready to handle the request (maintenance or overloaded).
The server is acting as a gateway and cannot get a response in time.
The HTTP version used in the request is not supported by the server.
1xx: Informational responses
2xx: Successful responses
3xx: Redirection messages
4xx: Client error responses
5xx: Server error responses