HTML, colors, ASCII and HTTP

HTTP Status Codes

A clear reference for HTTP status codes used by browsers, crawlers, APIs and web servers.

HTTP response codes

Status codes tell browsers, crawlers and API clients what happened to a request. Successful pages normally return 200, permanent redirects use 301 or 308, missing pages return 404, and server failures use 5xx responses.

CodeStatusMeaning
100ContinueThe initial part of a request has been received and the client can continue.
101Switching ProtocolsThe server is switching protocols as requested by the client.
102ProcessingThe server has received and is processing the request.
103Early HintsThe server is sending headers before the final response.
200OKThe request succeeded.
201CreatedThe request succeeded and a new resource was created.
202AcceptedThe request has been accepted for processing.
203Non-Authoritative InformationThe returned metadata is from a local or third-party copy.
204No ContentThe request succeeded and there is no body to return.
205Reset ContentThe client should reset the document view.
206Partial ContentThe server is returning part of the resource.
300Multiple ChoicesMore than one response is available.
301Moved PermanentlyThe resource has a new permanent URL.
302FoundThe resource is temporarily available at another URL.
303See OtherThe client should retrieve the response from another URL with GET.
304Not ModifiedThe cached version can be used.
307Temporary RedirectThe request should be repeated at another URL with the same method.
308Permanent RedirectThe resource has permanently moved and the method should not change.
400Bad RequestThe server cannot process the request because the syntax is invalid.
401UnauthorizedAuthentication is required or has failed.
403ForbiddenThe server understood the request but refuses access.
404Not FoundThe requested resource could not be found.
405Method Not AllowedThe HTTP method is not allowed for the resource.
408Request TimeoutThe server timed out waiting for the request.
409ConflictThe request conflicts with the current state of the resource.
410GoneThe resource is no longer available.
414URI Too LongThe requested URL is longer than the server can process.
418I am a teapotA playful status code from RFC 2324.
429Too Many RequestsThe client has sent too many requests in a given time.
451Unavailable For Legal ReasonsAccess is unavailable because of legal demand.
500Internal Server ErrorThe server encountered an unexpected condition.
501Not ImplementedThe server does not support the requested functionality.
502Bad GatewayA gateway or proxy received an invalid response.
503Service UnavailableThe server is temporarily unable to handle the request.
504Gateway TimeoutA gateway or proxy timed out waiting for an upstream server.
505HTTP Version Not SupportedThe server does not support the HTTP version used.