HTTP Status Codes

The complete reference guide to HTTP response codes. Optimized for quick scanning and debugging.

CodeStatusDescription
100ContinueThe client should continue the request or ignore the response if the request is already finished.
101Switching ProtocolsThe server is switching protocols as requested by the client (e.g., to WebSocket).
200OKThe request succeeded. The result meaning depends on the HTTP method.
201CreatedThe request succeeded, and a new resource was created as a result.
202AcceptedThe request has been received but not yet acted upon.
204No ContentThere is no content to send for this request, but the headers may be useful.
301Moved PermanentlyThe URL of the requested resource has been changed permanently.
302FoundThe URL of the requested resource has been changed temporarily.
304Not ModifiedThe client response is already cached and hasn't changed.
307Temporary RedirectThe server sends this response to direct the client to get the requested resource at another URI with same method.
308Permanent RedirectThis means that the resource is now permanently located at another URI.
400Bad RequestThe server could not understand the request due to invalid syntax.
401UnauthorizedThe client must authenticate itself to get the requested response.
403ForbiddenThe client does not have access rights to the content.
404Not FoundThe server can not find the requested resource.
405Method Not AllowedThe request method is known by the server but is not supported by the target resource.
408Request TimeoutThe server would like to shut down this unused connection.
429Too Many RequestsThe user has sent too many requests in a given amount of time ("rate limiting").
500Internal Server ErrorThe server has encountered a situation it does not know how to handle.
502Bad GatewayThis error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
503Service UnavailableThe server is not ready to handle the request (e.g., down for maintenance).
504Gateway TimeoutThis error response is given when the server could not get a response in time.

# Understanding HTTP Status Codes

HTTP status codes are essential indicators of the relationship between the client (browser) and the server. They are grouped into five classes, each representing a different category of response.

1xx InformationalRequest received, continuing process.
2xx SuccessThe action was successfully received, understood, and accepted.
3xx RedirectionFurther action must be taken in order to complete the request.
4xx Client ErrorThe request contains bad syntax or cannot be fulfilled.
5xx Server ErrorThe server failed to fulfill an apparently valid request.