HTTP response codes
HTTPResponse Codes indicate whether a specic HTTP requests has been successfully completed. Responses
are grouped in ve classes: informational responses, successful responses, redirections, client errors, and servers
errors.
The following table lists them all, with their respective meanings:
Status
code
Status text
Description
HTTP
version
Informational responses
This interim response indicates that everything so far is OK and that
100
Continue
the client should continue with the request or ignore it if it is already
nished.
HTTP/1.1
only
This code is sent in response to an Upgrade: request header by the
101
Switching
Protocol
client, and indicates that the protocol the server is switching too. It
was introduced to allow migration to an incompatible protocol
version, and is not in common use.
HTTP/1.1
only
Successful responses
The request has succeeded. The meaning of a success varies
depending on the HTTP method:
GET: The resource has been fetched and is transmitted in the
message body.
200
OK
HEAD: The entity headers are in the message body.
POST: The resource describing the result of the action is
transmitted in the message body.
HTTP/0.9
and later
TRACE: The message body contains the request message as
received by the server
201
202
Created
Accepted
The request has succeeded and a new resource has been created as
a result of it. This is typically the response sent after a PUTrequest.
The request has been received but not yet acted upon. It is noncommittal, meaning that there is no way in HTTP to later send an
asynchronous response indicating the outcome of processing the
request. It is intended for cases where another process or server
HTTP/0.9
and later
HTTP/0.9
and later
handles the request, or for batch processing.
203
NonAuthoritative
Information
204
No Content
This response code means returned meta-information set is not
exact set as available from the origin server, but collected from a
local or a third party copy. Except this condition, 200 OK response
should be preferred instead of this response.
There is no content to send for this request, but the headers may be
useful. The user-agent may update its cached headers for this
resource with the new ones.
205
206
HTTP/0.9
and 1.1
HTTP/0.9
and later
This response code is sent after accomplishing request to tell user
HTTP/1.1
agent reset document view which sent this request.
only
Partial
This response code is used because of range header sent by the
HTTP/1.1
Content
client to separate download into multiple streams.
only
Reset Content
Redirection messages
300
301
302
Multiple
Choice
The request has more than one possible responses. User-agent or
user should choose one of them. There is no standardized way to
choose one of the responses.
HTTP/1.0
and later
Moved
This response code means that URI of requested resource has been
HTTP/0.9
Permanently
changed. Probably, new URI would be given in the response.
and later
This response code means that URI of requested resource has been
changed temporarily. New changes in the URI might be made in the
HTTP/0.9
future. Therefore, this same URI should be used by the client in
and later
Found
future requests.
See Other
Server sent this response to directing client to get requested
resource to another URI with an GET request.
HTTP/0.9
and 1.1
304
Not Modied
This is used for caching purposes. It is telling to client that response
has not been modied. So, client can continue to use same cached
version of response.
HTTP/0.9
and later
305
Use Proxy
This means requested response must be accessed by a proxy. This
response code is not largely supported because security reasons.
HTTP/1.1
only
306
unused
This response code is no longer used, it is just reserved currently. It
was used in a previous version of the HTTP 1.1 specication.
HTTP/1.1
only
303
307
Temporary
Redirect
Server sent this response to directing client to get requested
resource to another URI with same method that used prior request.
This has the same semantic than the 302Found HTTP response
code, with the exception that the user agent must not change the
HTTP method used: if a POST was used in the rst request, a POST
must be used in the second request.
HTTP/1.1
only
This means that the resource is now permanently located at another
URI, specied by the Location: HTTP Response header. This has the
same semantics as the 301MovedPermanently HTTP response
code, with the exception that the user agent must not change the
308
Permanent
Redirect
HTTP method used: if a POST was used in the rst request, a POST
must be used in the second request.
draft-
reschkehttp-status308
Note: This is an experimental response code whose specication is
currently in draft form.
Client error responses
400
Bad Request
401
Unauthorized
402
Payment
Required
403
Forbidden
404
Not Found
405
Method Not
Allowed
406
Not
Acceptable
407
Proxy
Authentication
Required
This response means that server could not understand the request
due to invalid syntax.
HTTP/0.9
and later
Authentication is needed to get requested response. This is similar
HTTP/0.9
to 403, but in this case, authentication is possible.
and later
This response code is reserved for future use. Initial aim for creating
this code was using it for digital payment systems however this is not
HTTP/0.9
used currently.
and 1.1
Client does not have access rights to the content so server is
HTTP/0.9
rejecting to give proper response.
and later
Server can not nd requested resource. This response code probably
HTTP/0.9
is most famous one due to its frequency to occur in web.
and later
The request method is known by the server but has been disabled
and cannot be used. The two mandatory methods,GET and HEAD,
must never be disabled and should not return this error code.
HTTP/1.1
only
This response is sent when the web server, after performing serverdriven content negotiation, doesn't nd any content following the
criteria given by the user agent.
HTTP/1.1
only
This is similar to 401 but authentication is needed to be done by a
HTTP/1.1
proxy.
only
This response is sent on an idle connection by some servers, even
without any previous request by the client. It means that the server
would like to shut down this unused connection. This response is
408
Request
Timeout
used much more since some browsers, like Chrome or IE9, use
HTTP preconnection mechanisms to speed up surng (see
bug881804, which tracks the future implementation of such a
mechanism in Firefox). Also note that some servers merely shut
HTTP/1.1
only
down the connection without sending this message.
state of server.
HTTP/1.1
only
This response would be sent when requested content has been
deleted from server.
HTTP/1.1
only
Length
Required
Server rejected the request because the ContentLength header
eld is not dened and the server requires it.
HTTP/1.1
only
412
Precondition
Failed
The client has indicated preconditions in its headers which the server
does not meet.
HTTP/1.1
only
413
Payload Too
Large
Request entity is larger than limits dened by server; the server
might close the connection or return an RetryAfter header eld.
HTTP/1.1
only
414
URI Too Long
The URI requested by the client is longer than the server is willing to
HTTP/1.1
interpret.
only
415
Unsupported
Media Type
The media format of the requested data is not supported by the
server, so the server is rejecting the request.
HTTP/1.1
only
The range specied by the Range header eld in the request can't be
416
Requested
Range Not
Satisable
417
Expectation
Failed
This response code means the expectation indicated by the Expect
409
Conict
410
Gone
411
418
I'm a teapot
This response would be sent when a request conict with current
fullled; it's possible that the range is outside the size of the target
URI's data.
HTTP/1.1
only
request header eld can't be met by the server.
HTTP/1.1
only
Any attempt to brew coee with a teapot should result in the error
code "418 I'm a teapot". The resulting entity body MAY be short and
HTCPCP/1.0
stout.
The request was directed at a server that is not able to produce a
421
426
Misdirected
Request
Upgrade
Required
response. This can be sent by a server that is not congured to
produce responses for the combination of scheme and authority
that are included in the request URI.
The server refuses to perform the request using the current protocol
but might be willing to do so after the client upgrades to a dierent
protocol. The server MUST send an Upgrade header eld in a 426
response to indicate the required protocol(s) ( Section 6.7 of
[RFC7230]).
HTTP/2.0
HTTP/1.1
and later
The origin server requires the request to be conditional. Intended to
428
Precondition
Required
prevent "the 'lost update' problem, where a client GETs a resource's
state, modies it, and PUTs it back to the server, when meanwhile a
third party has modied the state on the server, leading to a
HTTP/1.1
and later
conict."
429
431
Too Many
The user has sent too many requests in a given amount of time
HTTP/1.1
Requests
("rate limiting").
and later
Request
Header Fields
The server is unwilling to process the request because its header
elds are too large. The request MAY be resubmitted after reducing
Too Large
the size of the request header elds.
HTTP/1.1
and later
Server error responses
500
Internal
Server Error
501
Not
Implemented
The server has encountered a situation it doesn't know how to
handle.
The request method is not supported by the server and cannot be
handled. The only methods that servers are required to support (and
therefore that must not return this code) are GETand HEAD.
This error response means that the server, while working as a
502
Bad Gateway
gateway to get a response needed to handle the request, got an
invalid response.
HTTP/0.9
and later
HTTP/0.9
and later
HTTP/0.9
and later
The server is not ready to handle the request. Common causes are a
server that is down for maintenance or that is overloaded. Note that
together with this response, a user-friendly page explaining the
503
Service
Unavailable
problem should be sent. This responses should be used for
temporary conditions and the RetryAfter: HTTPheader should, if
possible, contain the estimated time before the recovery of the
HTTP/0.9
and later
service. The webmaster must also take care about the cachingrelated headers that are sent along with this response, as these
temporary condition responses should usually not be cached.
504
Gateway
Timeout
This error response is given when the server is acting as a gateway
and cannot get a response in time.
HTTP Version
505
506
Not
Supported
The HTTP version used in the request is not supported by the server.
Variant Also
The server has an internal conguration error: transparent content
Negotiates
negotiation for the request results in a circular reference.
HTTP/1.1
only
HTTP/1.1
only
HTTP/1.1
The server has an internal conguration error: the chosen variant
507
Variant Also
Negotiates
Network
511
Authentication
Required
resource is congured to engage in transparent content negotiation
itself, and is therefore not a proper end point in the negotiation
process.
The 511 status code indicates that the client needs to authenticate to
gain network access.
HTTP/1.1
HTTP/1.1
