Documente Academic
Documente Profesional
Documente Cultură
100 Continue This code informs the client that it should proceed with its request. This is useful when the client is sending a large message body. After sending the headers, the client waits for the 100 response, and then proceeds to send the message body. 101 Switching Protocols This code allows clients and servers to negotiate the use of an alternate transfer protocol, or a different version of HTTP.
3xx Redirects
300 Multiple Choices This code informs users and user agents that the resource is available at multiple locations, perhaps in different representations. 301 Moved Permanently This code redirects clients to a new location for the requested resource. This happens often when people relocate files on their servers, or when content is moved from one server to another. Because the redirection is permanent, clients and caches can remember the new location and automatically redirect future requests. 302 Moved Temporarily This code is a temporary redirect to a new location. Apparently, many user agents always issue GET requests for the new URI, regardless of the original request method. This action violates even the older HTTP RFCs (1945 and 2068), but has
become the expected behavior. RFC 2616 added two new status codes, 303 and 307, to ``fix'' this problem. 303 See Other This code is the same as 302, except that the client should make a GET request for the new URI, regardless of the original request method. 304 Not Modified This code is used when the client makes a conditional GET request (e.g. If-modifiedsince) and the resource has not changed. 305 Use Proxy This code allows origin servers to redirect requests through a caching proxy. The proxy's address is given in the Location header. 306 Unused A search of the HTTP working group archives reveals that, at one time, this code was named Switch Proxy. 307 Temporary Redirect This code is similar to 302, indicating a temporary new location for the resource. However, clients must not use a different request method when requesting the new URI.
This code is used when a server times out waiting for the client's request. 409 Conflict This code indicates the server's resource is in a state of conflict, such that it cannot satisfy the request. Presumably, the user will be able to resolve the conflict after receiving this response. 410 Gone This code is used when an origin server knows that the requested resource has been permanently removed. 411 Length Required This code is used when the server requires, but did not receive, a &Contlen; header in the client's request. Requests for some methods, such as POST and PUT, have message bodies by default and therefore require &Contlen; headers. 412 Precondition Failed This code indicates that the request was unsuccessful because one of the client's conditions was not met. For example, the client can tell the server ``only update this resource if the current version is X.'' If the current version is not ``X,'' the server returns a 412 response. 413 Request Entity Too Large This code is used when a client's request is larger than the server is willing to accept. 414 Request-URI Too Large This code indicates that the requested URI exceeds the server's limits. Although servers should accept URIs of any length, practical considerations may require actual limits. 415 Unsupported Media Type This code is returned when a server refuses a request because the message body is in an inappropriate format. 416 Requested Range Not Satisfiable This code indicates that the server could not process the client's partial GET request. 417 Expectation Failed This code indicates that the client's expectation, given in an Expect header, can not be met. HTTP/1.1 clients typically use the Expect header to tell the server they expect to receive a 100 (Continue) status line.
This code is used by proxies and some servers to indicate a timeout when forwarding the client's request. It's also used when a request with the only-if-cached directive would result in a cache miss. 505 HTTP Version not supported This code indicates that the server refuses to handle this request because of the HTTP version in the request line.