23 server connection. The server responds with a status, which includes the message's |
23 server connection. The server responds with a status, which includes the message's |
24 protocol version and a success or error code, and a MIME-like message containing |
24 protocol version and a success or error code, and a MIME-like message containing |
25 server information, meta information, and body content. The following image |
25 server information, meta information, and body content. The following image |
26 illustrates a simple HTTP session between a client and a server. </p> <fig id="GUID-784DD05A-B86B-57F0-A2E0-A34E373ABA34"> |
26 illustrates a simple HTTP session between a client and a server. </p> <fig id="GUID-784DD05A-B86B-57F0-A2E0-A34E373ABA34"> |
27 <title> Simple HTTP Interaction </title> |
27 <title> Simple HTTP Interaction </title> |
28 <image href="GUID-18547A2C-7425-5478-8235-EC6D3848B404_d0e207449_href.png" placement="inline"/> |
28 <image href="GUID-18547A2C-7425-5478-8235-EC6D3848B404_d0e212456_href.png" placement="inline"/> |
29 </fig> <p>See <xref href="http://www.ietf.org/rfc/rfc2616.txt" scope="external">Hypertext |
29 </fig> <p>See <xref href="http://www.ietf.org/rfc/rfc2616.txt" scope="external">Hypertext |
30 Transfer Protocol -- HTTP/1.1, RFC 2616</xref> for more details. </p> </section> |
30 Transfer Protocol -- HTTP/1.1, RFC 2616</xref> for more details. </p> </section> |
31 <section id="GUID-80DD2A3D-1C59-4AD5-8838-8DC9E1752729"><title>Architectural |
31 <section id="GUID-80DD2A3D-1C59-4AD5-8838-8DC9E1752729"><title>Architectural |
32 relationships</title> <p>The HTTP Client architecture provides a generalised |
32 relationships</title> <p>The HTTP Client architecture provides a generalised |
33 mechanism for HTTP-like protocols that operate over various transports. Using |
33 mechanism for HTTP-like protocols that operate over various transports. Using |