The server has received the request headers and the client should proceed to send the request body.
101
Switching Protocols
Informational
The requester has asked the server to switch protocols and the server has agreed to do so.
102
Processing
Informational
The server has received and is processing the request, but no response is available yet.
The request was successful and the server has returned the requested data.
The request was successful and a new resource was created as a result.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request but is not returning any content.
206
Partial Content
Success
The server is delivering only part of the resource due to a range header sent by the client.
301
Moved Permanently
Redirection
The requested resource has been permanently moved to a new URL.
The requested resource resides temporarily under a different URL.
304
Not Modified
Redirection
The resource has not been modified since the version specified by the request headers.
307
Temporary Redirect
Redirection
The requested resource resides temporarily under a different URL. Method and body must not be changed.
308
Permanent Redirect
Redirection
The requested resource has been permanently moved to another URL. Method and body must not be changed.
400
Bad Request
Client Error
The server cannot or will not process the request due to an apparent client error.
401
Unauthorized
Client Error
Authentication is required and has failed or has not yet been provided.
The server understood the request but refuses to authorize it.
The requested resource could not be found on the server.
405
Method Not Allowed
Client Error
The method specified in the request is not allowed for the resource identified by the request URI.
408
Request Timeout
Client Error
The server timed out waiting for the request.
The request could not be processed because of conflict in the request.
The requested resource is no longer available and will not be available again.
413
Payload Too Large
Client Error
The request is larger than the server is willing or able to process.
418
I'm a teapot
Client Error
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol.
422
Unprocessable Entity
Client Error
The request was well-formed but was unable to be followed due to semantic errors.
429
Too Many Requests
Client Error
The user has sent too many requests in a given amount of time.
500
Internal Server Error
Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501
Not Implemented
Server Error
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502
Bad Gateway
Server Error
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503
Service Unavailable
Server Error
The server is currently unavailable (because it is overloaded or down for maintenance).
504
Gateway Timeout
Server Error
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
