Exit Zen
21
../../protocols/http.rst:100
English
More complex HTML elements can also include optional attributes in the start tag ::
0/830 · 83
22
../../protocols/http.rst:104
English
The HTML document shown below is composed of two parts: a header, delineated by the `<head>` and `</head>` markers, and a body (between the `<body>` and `</body>` markers). In the example below, the header only contains a title, but other types of information can be included in the header. The body contains an image, some text and a list with three hyperlinks. The image is included in the web page by indicating its URI between brackets inside the `<img src="...">` marker. It is important to note that the image can reside on any server. The client will automatically download it when rendering the web page. The `<h1>...</h1>` marker is used to specify the first level of headings. The `<ul>` marker indicates an unnumbered list while the `<li>` marker indicates a list item. The `<a href="URI">text</a>` indicates a hyperlink. The `text` will be underlined in the rendered web page and the client will fetch the specified URI when the user clicks on the link.
0/9650 · 965
23
../../protocols/http.rst:110
English
A simple HTML page
0/180 · 18
24
../../protocols/http.rst:112
English
Over the years, various extensions to HTML have been proposed and implemented. These include the specification of style sheets that adjust the layout of the document and the possibility of adding or referencing javascript code. Additional details about the various extensions to HTML may be found in the `official specifications <http://www.w3.org/MarkUp/>`_ maintained by W3C_.
0/3780 · 378
25
../../protocols/http.rst:114
English
The third component of the `world wide web` is the HyperText Transfer Protocol (HTTP). HTTP is a text-based protocol like SMTP. The client sends a request and the server returns a response. HTTP runs above the bytestream service and HTTP servers listen by default on port `80`. The design of HTTP has largely been inspired by the Internet email protocols. Each HTTP request contains three parts :
0/3960 · 396
26
../../protocols/http.rst:116
English
a `method`, that indicates the type of request, a URI, and the version of the HTTP protocol used by the client
0/1100 · 110
27
../../protocols/http.rst:117
English
a `header`, that is used by the client to specify optional parameters for the request. An empty line is used to mark the end of the header
0/1380 · 138
28
../../protocols/http.rst:118
English
an optional MIME document attached to the request
0/490 · 49
29
../../protocols/http.rst:120
English
The response sent by the server also contains three parts :
0/590 · 59
30
../../protocols/http.rst:122
English
a `status line` , that indicates whether the request was successful or not
0/740 · 74
31
../../protocols/http.rst:123
English
a `header`, that contains additional information about the response. The response header ends with an empty line.
0/1130 · 113
32
../../protocols/http.rst:124
English
a MIME document
0/150 · 15
33
../../protocols/http.rst:144
English
Several types of method can be used in HTTP requests. The three most important ones are :
0/890 · 89
34
../../protocols/http.rst:146
English
the `GET` method is the most popular one. It is used to retrieve a document from a server. The `GET` method is encoded as `GET` followed by the path of the URI of the requested document and the version of HTTP used by the client. For example, to retrieve the http://www.w3.org/MarkUp/ URI, a client must open a TCP connection on port `80` with host `www.w3.org` and send a HTTP request containing the following line:
0/4160 · 416
35
../../protocols/http.rst:152
English
the `HEAD` method is a variant of the `GET` method that allows the retrieval of the header lines for a given URI without retrieving the entire document. It can be used by a client to verify if a document exists, for instance.
0/2250 · 225
36
../../protocols/http.rst:153
English
the `POST` method can be used by a client to send a document to a server. The document is attached to the HTTP request as a MIME document.
0/1380 · 138
37
../../protocols/http.rst:156
English
HTTP clients and servers can include different HTTP headers in HTTP requests and responses. Each HTTP header is encoded as a single ASCII-line terminated by `CR` and `LF`. Several of these headers are briefly described below. A detailed discussion of the standard headers may be found in :rfc:`1945`. The MIME headers can appear in both HTTP requests and HTTP responses.
0/3700 · 370
38
../../protocols/http.rst:158
English
the `Content-Length:` header is the :term:`MIME` header that indicates the length of the MIME document in bytes.
0/1120 · 112
39
../../protocols/http.rst:159
English
the `Content-Type:` header is the :term:`MIME` header that indicates the type of the attached MIME document. HTML pages use the `text/html` type.
0/1450 · 145
40
../../protocols/http.rst:160
English
the `Content-Encoding:` header indicates how the :term:`MIME document` has been encoded. For example, this header would be set to `x-gzip` for a document compressed using the gzip_ software.
0/1900 · 190