1xx Informational
100
Continue
The server has received the request headers
101
Switching Protocols
The server is switching protocols
2xx Success
200
OK
The request was successful
201
Created
The request was successful and a new resource was created
204
No Content
The request was successful but there is no content to return
206
Partial Content
The server is delivering only part of the resource
3xx Redirection
301
Moved Permanently
The resource has been permanently moved to a new URL
302
Found
The resource has been temporarily moved to a different URL
304
Not Modified
The resource has not been modified since the last request
307
Temporary Redirect
The request should be repeated with another URI, method preserved
308
Permanent Redirect
The request and all future requests should use another URI
4xx Client Error
400
Bad Request
The server cannot process the request due to client error
401
Unauthorized
Authentication is required and has failed or not been provided
403
Forbidden
The server understood the request but refuses to authorize it
404
Not Found
The requested resource could not be found
405
Method Not Allowed
The request method is not supported for the requested resource
408
Request Timeout
The server timed out waiting for the request
409
Conflict
The request conflicts with the current state of the server
413
Payload Too Large
The request entity is larger than limits defined by server
415
Unsupported Media Type
The media format of the requested data is not supported
418
I'm a Teapot
The server refuses to brew coffee because it is a teapot (RFC 2324)
422
Unprocessable Entity
The request was well-formed but unable to be followed due to semantic errors
429
Too Many Requests
The user has sent too many requests in a given amount of time
5xx Server Error
500
Internal Server Error
The server encountered an unexpected condition
502
Bad Gateway
The server received an invalid response from the upstream server
503
Service Unavailable
The server is not ready to handle the request
504
Gateway Timeout
The server did not receive a timely response from the upstream server