HTTP status codes reference

Below is a reference table of HTTP status codes:

Status Code Description
100 Continue. The server has received the request headers and the client should continue with the request.
101 Switching Protocols. The requester has asked the server to switch protocols and the server is acknowledging that it will do so.
200 OK. The request has succeeded. The information returned with the response is dependent on the method used in the request.
201 Created. The request has been fulfilled and resulted in a new resource being created.
202 Accepted. The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information. The request was successful, but the information returned is not from the origin server and may be from a third-party source.
204 No Content. The request has succeeded, but the server has not returned any information.
205 Reset Content. The server has fulfilled the request and the user agent should reset the document view.
206 Partial Content. The server has fulfilled the partial GET request for the resource.
300 Multiple Choices. The requested resource has multiple choices and the user must select one of them.
301 Moved Permanently. The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the new URIs.
302 Found. The requested resource resides temporarily under a different URI.
303 See Other. The server has fulfilled the request, but the user agent should use the new URI provided in the response for future requests.
304 Not Modified. The requested resource has not been modified.
305 Use Proxy. The requested resource must be accessed through the proxy given by the location field.
307 Temporary Redirect. The requested resource resides temporarily under a different URI.
400 Bad Request. The request cannot be fulfilled due to bad syntax.
401 Unauthorized. The request requires user authentication.
402 Payment Required. This code is reserved for future use.
403 Forbidden. The server understood the request