HTTP message body

HTTP
Persistence Compression HTTPS
Request methods
OPTIONS GET HEAD POST PUT DELETE TRACE CONNECT PATCH
Header fields
Cookie ETag Location HTTP referer DNT X-Forwarded-For
Status codes
301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons

HTTP Message Body is the data bytes transmitted in an HTTP transaction message immediately following the headers if there is any (in the case of HTTP/0.9 no headers are transmitted).

HTTP message

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). The empty line must consist of only <CR><LF> and no other whitespace.

The "optional HTTP message body data" is what this article defines.

Response example

This could be a response from the web server:

HTTP/1.1 200 OK
Date: Sun, 10 Oct 2010 23:26:07 GMT
Server: Apache/2.2.8 (Ubuntu) mod_ssl/2.2.8 OpenSSL/0.9.8g
Last-Modified: Sun, 26 Sep 2010 22:04:35 GMT
ETag: "45b6-834-49130cc1182c0"
Accept-Ranges: bytes
Content-Length: 13
Connection: close
Content-Type: text/html

Hello world!

Syntax and supporting technologies	HTTP IRI URI RDF triples RDF/XML JSON-LD Turtle Notation3 N-Triples TriX (no W3C standard) RRID SPARQL XML

Schemas, ontologies and rules	Common logic OWL RDFS Rule Interchange Format Semantic Web Rule Language ALPS

Semantic annotation	eRDF GRDDL Microdata Microformats RDFa SAWSDL Facebook Platform

Common vocabularies	DOAP Dublin Core FOAF hAtom hCalendar hCard hProduct hRecipe hResume hReview SIOC SKOS

This article is issued from Wikipedia - version of the 11/24/2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.

HTTP message body

HTTP message

Response example

See also