HTTP Status Codes Flashcards
100
Continue
The client should continue sending its request. This is a special status code.
101
Switching Protocol
The client has used the Upgrade header to request the user of an alternative protocol and the server has agreed
200
OK
This is the generic successful Request message response, which is the code sent most often when a request is filled normally
201
Created
The request was successful and resulted in a resource being created. This is a typical response to a PUT method
202
Accepted
The request was accepted by the server, but it has not yet been processed. This is an intentionally noncommittal response that does not tell the client whether or not the request will be carried out. The client determines the eventual disposition of the request in some unspecified way. It is only used in special circumstances.
203
Non-Authoritative Source
The request was successful, but some of the information returned by the server came from a third party, rather than from the original server associated with the resource
204
No Content
The request was successful, but the server has determined that it does not need to return to the client an entity body
205
Reset Content
The request was successful; the server is telling the client that it should reset the document from which the request was generated so that a duplicate request is not sent. This code is intended for use with forms.
206
Partial Content
The server has successfully fulfilled a partial GET request.
300
Multiple Choices
The resource is represented in more than one way on the server. The server is returning information describing these representations, so the client can pick the most appropriate one, a process called agent-driven negotiation.
301
Moved Permanently
The resource requested has been moved to a new URL permanently. Any future requests for this resource should use the new URL. This is the proper method of handling situations where a file on a server is renamed or moved to a new directory. Most people don’t bother setting this up, which is wy URLs break so often, resulting in 404 errors.
302
Found
The resource requested is temporarily using a different URL. The client should continue to use the original URL.
303
See Other
The response for the request can be found at a different URL, which the server specifies. The client must do a fresh GET on that URL to see the results of the prior result.
304
Not Modified
The client sent a conditional GET request, but the resource has not been modified since the specified data/time, so the server has not sent it.
305
Use Proxy
To access the requested resource, the client must use a proxy, whose URL is given by the server in its response.
306
(unused)
Defined in an earlier version of HTTP and no longer used
103
Early Hints
This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.
307
Temporary Redirect
The resource is temporarily located at a different URL than the one the client specified. Note that 302 and 307 are basically the same status code. Code 307 was created to clear up some confusion related to 302 that occurred in earlier versions of HTTP.
400
Bad Request
This is a generic response when the request cannot be understood or carried out due to a problem on the client’s end.
401
Unauthorized
The client is not authorized to access the resource. This is often returned if an attempt is made to access a resource protected by a password or some other means without the appropriate credentials
402
Payment Required
This is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.