B.1 Informational Status Codes

Status codes from 100 199 are classified as "Informational." They are not successes, failures, or redirections.

B.1.1 100 Continue

The 100 Continue response indicates that the server is ready to receive the body of the request. This is only used if the client asked for confirmation before sending the body, by using the Expect: 100-continue header in the request, as explained in "Predicting Success for Lengthy Requests" in Chapter 3, HTTP Mechanics. Servers must handle this feature, but clients aren't required to. As an example, a client might use the Expect header together with the Content-Length header in a PUT request to confirm that the server is willing to handle a file of a given size. If the server cannot, it should send 417 Expectation Failed.

Defined in HTTP/1.1.

B.1.2 101 Switching Protocols

101 Switching Protocols indicates that the server will now begin communicating using a different protocol. This is only used when the Upgrade header is sent in the request and the server decides to switch.

Defined in HTTP/1.1.

B.1.3 102 Processing

102 Processing is used by a WebDAV server to indicate that it is working on a time-consuming request. For example, a depth infinity MOVE request to a large collection could take some time to complete. Clients may time out lengthy requests under the assumption that the request was ignored or dropped somehow. This status code allows the server to let the client know that it shouldn't time out the request, that the server is still working on the real response. Clients must support this response code, since the server can return it in any time-consuming operation. Servers are not required to use this response code.

Defined in WebDAV.



WebDAV. Next Generation Collaborative Web Authoring
WebDAV. Next Generation Collaborative Web Authoring
ISBN: 130652083
EAN: N/A
Year: 2003
Pages: 146

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net