HTTP Status Codes Reference

Complete reference guide to all HTTP status codes. Browse by category or use the search to find specific codes.

  1. Home
  2. Web Dev
  3. HTTP Status Codes

Below is a complete list of HTTP status codes grouped by category. Click any code to see a detailed explanation including RFC references and common use cases.

Visible rows: 0
Code Title Category Description
100 Continue 1xx The server has received the request headers and the client should proceed to send the request body.
101 Switching Protocols 1xx The server is switching protocols as requested by the client via the Upgrade header.
102 Processing 1xx The server has received and is processing the request, but no response is available yet (WebDAV).
103 Early Hints 1xx The server can send early hints to preload resources while the final response is being prepared.
200 OK 2xx The request has succeeded. The meaning of the success depends on the HTTP method used.
201 Created 2xx The request has been fulfilled and has resulted in one or more new resources being created.
202 Accepted 2xx The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information 2xx The request was successful but the enclosed payload has been modified by a transforming proxy.
204 No Content 2xx The server has successfully fulfilled the request and there is no additional content to send.
205 Reset Content 2xx The server has fulfilled the request and desires that the user agent reset the document view.
206 Partial Content 2xx The server is delivering only part of the resource due to a range header sent by the client.
207 Multi-Status 2xx Provides status for multiple independent operations (WebDAV).
208 Already Reported 2xx The members of a DAV binding have already been enumerated in a preceding part of the response (WebDAV).
226 IM Used 2xx The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
300 Multiple Choices 3xx The target resource has more than one representation, each with its own specific location.
301 Moved Permanently 3xx The target resource has been assigned a new permanent URI and any future references should use the new URI.
302 Found 3xx The target resource resides temporarily under a different URI.
303 See Other 3xx The server is redirecting the user agent to a different resource that provides an indirect response to the request.
304 Not Modified 3xx A conditional GET request has been received and would have resulted in a 200 response if the condition was false.
305 Use Proxy 3xx The requested resource must be accessed through the proxy given by the Location field.
306 Unused 3xx This status code was used in a previous version of the specification and is no longer used.
307 Temporary Redirect 3xx The target resource resides temporarily under a different URI and the method must not change.
308 Permanent Redirect 3xx The target resource has been assigned a new permanent URI and the method must not change.
400 Bad Request 4xx The server cannot or will not process the request due to something perceived as a client error.
401 Unauthorized 4xx The request has not been applied because it lacks valid authentication credentials for the target resource.
402 Payment Required 4xx This status code is reserved for future use and is intended for digital payment systems.
403 Forbidden 4xx The server understood the request but refuses to authorize it.
404 Not Found 4xx The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
405 Method Not Allowed 4xx The method received in the request-line is known by the origin server but not supported by the target resource.
406 Not Acceptable 4xx The target resource does not have a current representation that would be acceptable to the user agent.
407 Proxy Authentication Required 4xx The client must first authenticate itself with the proxy.
408 Request Timeout 4xx The server did not receive a complete request message within the time it was prepared to wait.
409 Conflict 4xx The request could not be completed due to a conflict with the current state of the target resource.
410 Gone 4xx The target resource is no longer available at the origin server and this condition is likely permanent.
411 Length Required 4xx The server refuses to accept the request without a defined Content-Length header.
412 Precondition Failed 4xx One or more conditions given in the request header fields evaluated to false.
413 Content Too Large 4xx The request body is larger than the server is willing or able to process.
414 URI Too Long 4xx The target URI is longer than the server is willing to interpret.
415 Unsupported Media Type 4xx The origin server is refusing to service the request because the payload is in a format not supported.
416 Range Not Satisfiable 4xx None of the ranges in the request's Range header field overlap the current extent of the selected resource.
417 Expectation Failed 4xx The expectation given in the request's Expect header field could not be met.
418 I'm a Teapot 4xx This code was defined in 1998 as an April Fools' joke in RFC 2324, Hyper Text Coffee Pot Control Protocol.
421 Misdirected Request 4xx The request was directed at a server that is not able to produce a response.
422 Unprocessable Content 4xx The server understands the content type and syntax of the request body but was unable to process the contained instructions.
423 Locked 4xx The source or destination resource of a method is locked (WebDAV).
424 Failed Dependency 4xx The method could not be performed on the resource because the requested action depended on another action that failed (WebDAV).
425 Too Early 4xx The server is unwilling to risk processing a request that might be replayed.
426 Upgrade Required 4xx The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades.
428 Precondition Required 4xx The origin server requires the request to be conditional to prevent the lost update problem.
429 Too Many Requests 4xx The user has sent too many requests in a given amount of time (rate limiting).
431 Request Header Fields Too Large 4xx The server is unwilling to process the request because its header fields are too large.
451 Unavailable For Legal Reasons 4xx The server is denying access to the resource as a consequence of a legal demand.
500 Internal Server Error 5xx The server encountered an unexpected condition that prevented it from fulfilling the request.
501 Not Implemented 5xx The server does not support the functionality required to fulfill the request.
502 Bad Gateway 5xx The server, while acting as a gateway or proxy, received an invalid response from an inbound server.
503 Service Unavailable 5xx The server is currently unable to handle the request due to a temporary overload or scheduled maintenance.
504 Gateway Timeout 5xx The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
505 HTTP Version Not Supported 5xx The server does not support, or refuses to support, the major version of HTTP that was used in the request.
506 Variant Also Negotiates 5xx The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself.
507 Insufficient Storage 5xx The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
508 Loop Detected 5xx The server terminated an operation because it encountered an infinite loop while processing a request (WebDAV).
510 Not Extended 5xx The policy for accessing the resource has not been met in the request.
511 Network Authentication Required 5xx The client needs to authenticate to gain network access.