|
 |
The TCP/IP Guide
9 TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
9 TCP/IP Key Applications and Application Protocols
9 TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
9 TCP/IP World Wide Web (WWW, "The Web") and the Hypertext Transfer Protocol (HTTP)
9 TCP/IP Hypertext Transfer Protocol (HTTP)
9 HTTP Messages, Message Formats, Methods and Status Codes
|
HTTP Request Message Format
(Page 1 of 3)
The client initiates an HTTP session
by opening a TCP connection to the HTTP server with which it wishes
to communicate. It then sends request messages to the server,
each of which specifies a particular type of action that the user of
the HTTP client would like the server to take. Requests can be generated
either by specific user action (such as clicking a hyperlink in a Web
browser) or indirectly as a result of a prior action (such as a reference
to an inline image in an HTML document leading to a request for that
image.)
HTTP requests use a message format
that is based on the generic message format described in the
preceding topic, but specific to the needs
of requests. The structure of this format is as follows (see Figure 317):
<request-line>
<general-headers>
<request-headers>
<entity-headers>
<empty-line>
[<message-body>]
[<message-trailers>]
|
