The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD. A user agent should detect and intervene to prevent cyclical redirects.
Indicates multiple options for the resource from which the client may choose.
Since HTTP/1.0 did not define any 1xx status codes, servers must not The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request).
Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient.
To have a server check the request's headers, a client must send A Web DAV request may contain many sub-requests involving file operations, requiring a long time to complete the request.
This code indicates that the server has received and is processing the request, but no response is available yet. 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.
The server is delivering only part of the resource (byte serving) due to a range header sent by the client.
This is a list of Hypertext Transfer Protocol (HTTP) response status codes.
It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes.