|
 |
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 Response Message Format
(Page 1 of 3)
Up and down; east and west; black
and white; yin and yang. Well, you get the idea. Each request message
sent by an HTTP client to a server prompts the server to send back a
response message. Actually, in certain cases the server may in
fact send two responses, a preliminary response followed by the real
one. Usually though, one request yields one response, which indicates
the results of the server's processing of the request, and often also
carries an entity (file or resource) in the message body.
Like requests, responses use their
own specific message format that is based on the HTTP
generic message format. The format, shown
in Figure 318,
is:
<status-line>
<general-headers>
<response-headers>
<entity-headers>
<empty-line>
[<message-body>]
[<message-trailers>]
|
