status codes Flashcards
Learn the meaning of every http status code.
What do HTTP response status codes indicate?
How a specific HTTP request has completed.
What are the five HTTP status code classes?
1xx: Informational.
2xx: Successful.
3xx: Redirection.
4xx: Client Error.
5xx: Server Error.
100 status code?
Continue. Everything is OK so far and client should continue with request or ignore if it is already finished.
101 status code?
Switching Protocol. Response to an Upgrade request header by the client, and indicates the protocol the server is switching to.
102 status code?
Processing. Indicates that the server has received and is processing the request, but no response is available yet.
103 status code?
Early Hints. Primarily intended to be used with the Link header to allow the user agent to start preloading resources while the server is still preparing a response.
200 status code?
OK. 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.
HEAD: The entity headers are in the 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 status code?
Created. Request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a POST request, or after some PUT requests.
202 status code?
Accepted. The request has been received but not yet acted upon. It is non-committal, 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 handles the request, or for batch processing.
203 status code?
Non-Authoritative Information. 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.
204 status code?
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.
205 status code?
Reset Content. Sent after accomplishing request to tell user agent reset document view which sent this request.
206 status code?
Partial Content. Used because of range header sent by the client to separate download into multiple streams.
300 status code?
Multiple Choice. 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.
301 status code?
Moved Permanently. Means that the URI of the requested resource has been changed permanently. Probably, the new URI would be given in the response.
302 status code?
Found. Means that the URI of requested resource has been changed temporarily. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
303 status code?
See Other. The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304 status code?
Not Modified. This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
307 status code?
Temporary Redirect. The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.
308 status code?
Permanent Redirect. This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.