Text
HTTP Status Codes
Browse and search all standard HTTP status codes from 1xx to 5xx with names and descriptions.
No status codes match your search.
- 100 Continue The server has received the request headers and the client should proceed to send the request body.
- 101 Switching Protocols The server agrees to switch protocols as requested by the client via the Upgrade header.
- 200 OK The request succeeded and the response body contains the requested resource.
- 201 Created The request succeeded and a new resource was created as a result.
- 202 Accepted The request has been accepted for processing, but processing has not been completed.
- 204 No Content The request succeeded but there is no content to send in the response body.
- 206 Partial Content The server is delivering only part of the resource due to a Range header in the request.
- 301 Moved Permanently The requested resource has been permanently moved to a new URL.
- 302 Found The requested resource temporarily resides under a different URL.
- 303 See Other The response to the request can be found under a different URL using a GET method.
- 304 Not Modified The resource has not been modified since the version specified by the request headers.
- 307 Temporary Redirect The requested resource temporarily resides under a different URL and the method must not change.
- 308 Permanent Redirect The resource has permanently moved to a new URL and the method must not change.
- 400 Bad Request The server cannot process the request due to a client error such as malformed syntax.
- 401 Unauthorized Authentication is required and has failed or has not yet been provided.
- 403 Forbidden The server understands the request but refuses to authorize it.
- 404 Not Found The requested resource could not be found on the server.
- 405 Method Not Allowed The HTTP method used is not allowed for the requested resource.
- 406 Not Acceptable The server cannot produce a response matching the acceptable values defined in the request headers.
- 408 Request Timeout The server timed out waiting for the request from the client.
- 409 Conflict The request conflicts with the current state of the target resource.
- 410 Gone The requested resource is no longer available and has been permanently removed.
- 411 Length Required The server requires the Content-Length header to be specified in the request.
- 412 Precondition Failed One or more conditions given in the request header fields evaluated to false.
- 413 Content Too Large The request body exceeds the limits defined by the server.
- 414 URI Too Long The URI requested by the client is longer than the server is willing to interpret.
- 415 Unsupported Media Type The media format of the request is not supported by the server.
- 416 Range Not Satisfiable The range specified by the Range header cannot be satisfied by the current representation of the resource.
- 417 Expectation Failed The expectation indicated by the Expect request header could not be met by the server.
- 418 I'm a Teapot The server refuses to brew coffee because it is, permanently, a teapot.
- 422 Unprocessable Content The server understands the request entity but cannot process it due to semantic errors.
- 423 Locked The source or destination resource of a method is locked.
- 426 Upgrade Required The client should switch to the protocol specified in the Upgrade header.
- 428 Precondition Required The origin server requires the request to be conditional to prevent lost-update problems.
- 429 Too Many Requests The user has sent too many requests in a given amount of time (rate limiting).
- 431 Request Header Fields Too Large The server is unwilling to process the request because header fields are too large.
- 451 Unavailable For Legal Reasons The server is denying access to the resource as a consequence of a legal demand.
- 500 Internal Server Error The server encountered an unexpected condition that prevented it from fulfilling the request.
- 501 Not Implemented The server does not support the functionality required to fulfill the request.
- 502 Bad Gateway The server, acting as a gateway, received an invalid response from an upstream server.
- 503 Service Unavailable The server is temporarily unable to handle requests due to overload or maintenance.
- 504 Gateway Timeout The server, acting as a gateway, did not receive a timely response from an upstream server.
- 505 HTTP Version Not Supported The server does not support the HTTP protocol version used in the request.
- 511 Network Authentication Required The client needs to authenticate to gain network access, typically used by captive portals.