Tools / Web Tools / HTTP Status Codes

HTTP Status Codes

100Continue
The server has received the request headers and the client should proceed to send the body.
101Switching Protocols
The requester has asked the server to switch protocols.
102Processing
The server has received and is processing the request, but no response is available yet.
103Early Hints
Used to return some response headers before the final HTTP message.
200OK
The request succeeded.
201Created
The request succeeded and a new resource was created.
202Accepted
The request was accepted for processing, but processing is not complete.
203Non-Authoritative Information
The returned metadata is not from the origin server.
204No Content
The request succeeded but there is no content to send.
205Reset Content
Tells the client to reset the document that sent this request.
206Partial Content
Used for range requests, delivering only part of a resource.
207Multi-Status
Conveys information about multiple resources (WebDAV).
208Already Reported
Members of a DAV binding have already been enumerated (WebDAV).
226IM Used
The server fulfilled a GET request and the response is an instance-manipulation result.
300Multiple Choices
The request has more than one possible response.
301Moved Permanently
The URL of the requested resource has changed permanently.
302Found
The URI of the requested resource has changed temporarily.
303See Other
The response can be found under another URI using GET.
304Not Modified
The resource has not been modified since the last request.
305Use Proxy
Deprecated. The requested resource must be accessed through a proxy.
307Temporary Redirect
The request should be repeated with the same method at another URI.
308Permanent Redirect
The resource has permanently moved, method should not change.
400Bad Request
The server cannot process the request due to a client error.
401Unauthorized
Authentication is required and has failed or not been provided.
402Payment Required
Reserved for future use.
403Forbidden
The client does not have access rights to the content.
404Not Found
The server cannot find the requested resource.
405Method Not Allowed
The request method is known but not supported by the target resource.
406Not Acceptable
No content matching the criteria given by the client is available.
407Proxy Authentication Required
Authentication with a proxy is required.
408Request Timeout
The server timed out waiting for the request.
409Conflict
The request conflicts with the current state of the target resource.
410Gone
The requested content has been permanently deleted.
411Length Required
The Content-Length header was not specified.
412Precondition Failed
A precondition in the request headers was not met.
413Payload Too Large
The request entity is larger than limits the server will process.
414URI Too Long
The URI requested is longer than the server can interpret.
415Unsupported Media Type
The media format of the requested data is not supported.
416Range Not Satisfiable
The range specified cannot be fulfilled.
417Expectation Failed
The Expect request header could not be met.
418I'm a Teapot
The server refuses to brew coffee because it is a teapot (RFC 2324).
421Misdirected Request
The request was directed at a server unable to produce a response.
422Unprocessable Entity
The request was well-formed but has semantic errors.
423Locked
The resource being accessed is locked (WebDAV).
424Failed Dependency
The request failed due to failure of a previous request (WebDAV).
425Too Early
The server is unwilling to process a request that might be replayed.
426Upgrade Required
The client should switch to a different protocol.
428Precondition Required
The origin server requires the request to be conditional.
429Too Many Requests
The user has sent too many requests in a given amount of time.
431Request Header Fields Too Large
The server is unwilling to process request headers that are too large.
451Unavailable For Legal Reasons
The resource is unavailable for legal reasons.
500Internal Server Error
The server has encountered an unexpected condition.
501Not Implemented
The request method is not supported by the server.
502Bad Gateway
The server got an invalid response from an upstream server.
503Service Unavailable
The server is not ready to handle the request.
504Gateway Timeout
The upstream server failed to send a request in time.
505HTTP Version Not Supported
The HTTP version used in the request is not supported.
506Variant Also Negotiates
Transparent content negotiation results in a circular reference.
507Insufficient Storage
The server is unable to store the representation needed (WebDAV).
508Loop Detected
The server detected an infinite loop while processing (WebDAV).
510Not Extended
Further extensions to the request are required.
511Network Authentication Required
The client needs to authenticate to gain network access.