HTTP Codes Flashcards
100
Continue - server has received request headers, and client should proceed to send the request body.
101
Switching protocols - requester has asked the server to switch protocols, and the server is acknowledging it will do so.
102
Processing (WebDAV: rfc 2518). Indicates sever has received and is processing requests. But no response is available yet. Used to prevent timeouts.
200
OK - standard response for successful requests.
201
Created - the request has been fulfilled and resulted in a new resource being created.
202
Accepted - the request has been accepted for processing, but the processing is not completed. It may / may not be acted on, it may even be disallowed when processing actually takes place.
203
Non-authoritative information. The server successfully processed the request, but is returning information that may be from another source
204
No content - the server successfully completed the request, but is not returning any content (I.e. Delete requests)
205
Reset content - the server successfully processed the request, but not sending content, this is different to a 204, in that the response requires the requester reset the document view.
206
Partial content - server is only delivering part of the resource (byte serving) due to a range header sent by the client. Range header is used by tools like get to enable resuming of interrupted downloads, or splitting into simultaneous streams.
207
Multiple-status - the message body that follows is XML and can contains number of separate response codes, depending on number of sub requests made.
208
Already reported - the members of a DAV have already been enumerated in a previous reply to this request, and are not being included again.
226
IM Used - the server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance
300
Multiple choices - multiple choices may follow. Such as different format options for video.
301
Moved permanently - this and all future requests should be directed to the given URI.
302
Found - was usually implemented incorrectly, using meaning of a 303. Hence the need for the 303 and 307 codes
303
See other - the reponse to the request can be found under another URI using a get method. (Can be received in response to post, put or delete request)
304
Not modified - indicates the resource has not been modified since the version specified bt the request headers.
305
Use proxy - the requested resource is only available through a proxy, whose address is provided in the header.
306
Switch proxy - no longer used
307
Temporary redirect - the request should be repeat edits another URI. However future requests should still use the original URI.
308
Permanent redirect - the request and all future requests should be repeated using another URI.
400
Bad request - server cannot and will not process the request due to something that is perceived as a client error.
401
Unauthorised - Similar to 403 forbidden, but specifically when authorisation is required and has either failed, or not been provided.
