HTTP Response Status Codes - HTTP - MDN
HTTP Response Status Codes - HTTP - MDN
HTTP response status codes indicate whether a specific HTTP request has been successfully
completed.
Responses are grouped in five classes:
The below status codes are defined by section 10 of RFC 2616 . You can find an updated
specification in RFC 7231 .
Note: If you receive a response that is not in this list, it is a non-standard response, possibly
custom to the server's software.
Information responses
100 Continue
This interim response indicates that the client should continue the request or ignore the
response if the request is already finished.
Successful responses
200 OK
The request succeeded. The result meaning of "success" depends on the HTTP method:
GET : The resource has been fetched and transmitted in the message body.
HEAD : The representation headers are included in the response without any message
body.
PUT or POST : The resource describing the result of the action is transmitted in the
message body.
TRACE : The message body contains the request message as received by the server.
201 Created
The request succeeded, and a new resource was created as a result. This is typically the
response sent after POST requests, or some PUT requests.
202 Accepted
The request has been received but not yet acted upon.
It is noncommittal, since there is no
way in HTTP to later send an asynchronous response indicating the outcome of the
request.
It is intended for cases where another process or server handles the request, or for
batch processing.
204 No Content
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.
Conveys information about multiple resources, for situations where multiple status codes
might be appropriate.
Redirection messages
300 Multiple Choice
The request has more than one possible response. The user agent or user should choose
one of them. (There is no standardized way of choosing one of the responses, but HTML
links to the possibilities are recommended so the user can pick.)
302 Found
This response code means that the URI of requested resource has been changed
temporarily.
Further changes in the URI might be made in the future. Therefore, this same
URI should be used by the client in future requests.
401 Unauthorized
Although the HTTP standard specifies "unauthorized", semantically this response means
"unauthenticated".
That is, the client must authenticate itself to get the requested response.
403 Forbidden
The client does not have access rights to the content; that is, it is unauthorized, so the
server is refusing to give the requested resource.
Unlike 401 Unauthorized , the client's
identity is known to the server.
409 Conflict
This response is sent when a request conflicts with the current state of the server.
410 Gone
This response is sent when the requested content has been permanently deleted from
server, with no forwarding address.
Clients are expected to remove their caches and links to
the resource.
The HTTP specification intends this status code to be used for "limited-time,
promotional services".
APIs should not feel compelled to indicate resources that have been
deleted with this status code.
The client has indicated preconditions in its headers which the server does not meet.
Indicates that the server is unwilling to risk processing a request that might be replayed.
Browser compatibility