Exit Zen
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
41
../../protocols/http.rst:162
English
:rfc:`1945` and :rfc:`2616` define headers that are specific to HTTP responses. These server headers include:
0/1090 · 109
42
../../protocols/http.rst:164
English
the `Server:` header indicates the version of the web server that has generated the HTTP response. Some servers provide information about their software release and optional modules that they use. For security reasons, some system administrators disable these headers to avoid revealing too much information about their server to potential attackers.
0/3500 · 350
43
../../protocols/http.rst:165
English
the `Date:` header indicates when the HTTP response has been produced by the server.
0/840 · 84
44
../../protocols/http.rst:166
English
the `Last-Modified:` header indicates the date and time of the last modification of the document attached to the HTTP response.
0/1270 · 127
45
../../protocols/http.rst:168
English
Similarly, the following header lines can only appear inside HTTP requests sent by a client:
0/920 · 92