Search results
Results from the WOW.Com Content Network
The length of the request body in octets (8-bit bytes). Content-Length: 348: Permanent RFC 9110: Content-MD5: A Base64-encoded binary MD5 sum of the content of the request body. Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ== Obsolete [15] RFC 1544, 1864, 4021: Content-Type: The Media type of the body of the request (used with POST and PUT requests).
The request/response message consists of the following: Request line, such as GET /logo.gif HTTP/1.1 or Status line, such as HTTP/1.1 200 OK, Headers; An empty line; Optional HTTP message body data; The request/status line and headers must all end with <CR><LF> (that is, a carriage return followed by a line feed).
Each response header field has a defined meaning which can be further refined by the semantics of the request method or response status code. HTTP/1.1 example of request / response transaction Below is a sample HTTP transaction between an HTTP/1.1 client and an HTTP/1.1 server running on www.example.com , port 80.
The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. [2] All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role.
The HTTP response status code 303 See Other is a way to redirect web applications to a new URI, particularly after a HTTP POST has been performed, since RFC 2616 (HTTP 1.1). According to RFC 7231, which obsoletes RFC 2616, "A 303 response to a GET request indicates that the origin server does not have a representation of the target resource ...
If a Transfer-Encoding field with a value of "chunked" is specified in an HTTP message (either a request sent by a client or the response from the server), the body of the message consists of one or more chunks and one terminating chunk with an optional trailer before the final ␍␊ sequence (i.e. carriage return followed by line feed).
Starting with HTML 4.0, forms can also submit data in multipart/form-data as defined in RFC 2388 (See also RFC 1867 for an earlier experimental version defined as an extension to HTML 2.0 and mentioned in HTML 3.2). The special case of a POST to the same page that the form belongs to is known as a postback.
The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. [14] The request can be aborted prematurely [ 15 ] or set to fail if not completed in a specified amount of time.