Skip to content
ZeroServer.tools

HTTP Status Code Reference

Search and look up every HTTP status code and its meaning.

1xx — Informational

100
Continue
The client should continue the request or ignore if already finished.
101
Switching Protocols
The server is switching protocols as requested by the client.
102
Processing
The server has received and is processing the request (WebDAV).
103
Early Hints
Used to return some response headers before the final response.

2xx — Success

200
OK
The request succeeded. The meaning depends on the HTTP method.
201
Created
The request succeeded and a new resource was created.
202
Accepted
The request was received but not yet acted upon.
204
No Content
Success, but there is no content to send for this request.
206
Partial Content
The server is delivering only part of the resource (range request).

3xx — Redirection

301
Moved Permanently
The resource has a new permanent URL.
302
Found
The resource is temporarily at a different URL.
303
See Other
The response can be found under another URL using GET.
304
Not Modified
The cached version is still valid; no need to re-transfer.
307
Temporary Redirect
Temporary redirect that preserves the HTTP method.
308
Permanent Redirect
Permanent redirect that preserves the HTTP method.

4xx — Client Error

400
Bad Request
The server cannot process the request due to a client error.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The client is authenticated but not allowed to access the resource.
404
Not Found
The server cannot find the requested resource.
405
Method Not Allowed
The HTTP method is not supported for this resource.
406
Not Acceptable
No content matches the criteria in the request's Accept headers.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is permanently gone with no forwarding address.
413
Payload Too Large
The request body is larger than the server will process.
415
Unsupported Media Type
The request's media format is not supported.
418
I'm a teapot
An April Fools' joke code; the server refuses to brew coffee.
422
Unprocessable Entity
The request was well-formed but had semantic errors (WebDAV).
429
Too Many Requests
The client has sent too many requests in a given time (rate limited).
431
Request Header Fields Too Large
Header fields are too large for the server to process.
451
Unavailable For Legal Reasons
The resource is unavailable for legal reasons.

5xx — Server Error

500
Internal Server Error
A generic error; the server hit an unexpected condition.
501
Not Implemented
The server does not support the functionality to fulfill the request.
502
Bad Gateway
An upstream server sent an invalid response to the gateway.
503
Service Unavailable
The server is not ready — often overloaded or down for maintenance.
504
Gateway Timeout
An upstream server did not respond in time.
505
HTTP Version Not Supported
The HTTP version used in the request is not supported.
511
Network Authentication Required
The client must authenticate to gain network access.

Understanding HTTP status codes

Every HTTP response carries a three-digit status code that tells the client what happened. The first digit sets the class: 1xx informational, 2xx success, 3xx redirection, 4xx client errors, and 5xx server errors. Knowing the difference between, say, a 401 and a 403, or a 302 and a 308, saves real debugging time.

Building an API or a site? You might also want the MIME type lookup and the URL parser.

Related Developer Utilities tools