HTTP Status Codes Flashcards
(34 cards)
This tells the client to continue with the rest of it’s request.
100 Continue
This indicates that the server will switch to an updated HTTP version in response to a client request to do so.
101 Switching Protocols
The request was successful.
200 OK
Your request was successful and resulted in a new resource being created.
201 Created
Your request was accepted for processing; however, it may not have yet been processed.
202 Accepted
The information returned to you is not from the original source but may be from a third party or be a subset of the original information.
203 Non Authoritative Information
The request was successful but the response results in no content.
204 No Content
The client should reset the document view.
205 Reset Content
The server fulfilled the partial GET request.
206 Partial Content
The reply from the server will contain multiple resources the client can choose to redirect to.
300 Multiple Choices
This code is used when a resource will never again be available at the previous URI and has been moved to the new resource. Administrators use this code when they want to indicate that a client should point all future requests to the new URI.
301 Moved Permanently
Unlike the 301 status, this code denotes a resource that is only temporarily being redirected.
302 Found
This is commonly a response to a POST request, where the response can be obtained via a GET request to a different URI.
303 See Other
This response is used when the client sends a GET request conditional on the document being modified. This response lets the client know that the document has not changed.
304 Not Modified
The server will provide a proxy in its response URI that must be followed to access the requested data.
305 Use Proxy
Status code is not yet used.
306 Unused
This is similar to a 302 code and is used when the resource the client is requesting can be found under a different URI temporarily, but in the future, the client should use the original URI.
307 Temporary Redirect
This code is used in response to bad syntax on the client side.
400 Bad Request
This request requires authentication from the user, so the client should repeat the request with proper authentication.
401 Unauthorized
Unlike a 401, this request is not allowed from the user, and the client should not attempt to repeat the request with authentication. This error code is often indicative of permissions errors.
403 Forbidden
The server couldn’t find the page the client requested. This error code often comes up when the user had a typo in their request. when the request is for a page that has moved without a redirection put in place, or when the file used to exist but has been deleted.
404 Not Found
The client took too long to produce a request. You may see this when you are experimenting with the web server troubleshooting over telnet.
408 Request Timeout
Unlike a 3xx redirection request, this code is used when the resource used to exist but is now forever gone.
410 Gone
The server received some internal error when it was processing the request. You may see this when you have a bug in a CGI or PHP script that causes the file to error out when it is run.
500 Internal Server Error