Term
|
Definition
| Continue .. a client must send Expect: 100-continue as a header in its initial request[2] and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue) |
|
|
Term
|
Definition
| Switching Protocols ... means the requester has asked the server to switch protocols and the server is acknowledging that it will do so |
|
|
Term
|
Definition
| Processing (WEBDAV) .. Server would need more time to process the request |
|
|
Term
|
Definition
| Checkpoint .. Resumable HTTP Requests Proposal to resume aborted PUT or POST requests |
|
|
Term
|
Definition
Request-URI too long
This is a non-standard IE7-only code which means the URI is longer than a maximum of 2083 characters |
|
|
Term
|
Definition
| OK. Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action |
|
|
Term
|
Definition
Created
The request has been fulfilled and resulted in a new resource being created |
|
|
Term
|
Definition
Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. |
|
|
Term
|
Definition
Non-Authoritative Information (since HTTP/1.1)
The server successfully processed the request, but is returning information that may be from another source |
|
|
Term
|
Definition
No Content
The server successfully processed the request, but is not returning any content. |
|
|
Term
|
Definition
Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view. |
|
|
Term
|
Definition
Partial Content
The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. |
|
|
Term
|
Definition
Multi-Status (WebDAV) (RFC 4918)
The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. |
|
|
Term
|
Definition
IM Used (RFC 3229)
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance |
|
|
Term
|
Definition
Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation. |
|
|
Term
|
Definition
Moved Permanently ..
This and all future requests should be directed to the given URI |
|
|
Term
|
Definition
Found
This is an example of industrial practice contradicting the standard.[2] HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"),[9] but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[10] However, some Web applications and frameworks use the 302 status code as if it were the 303 |
|
|
