GridLab
Grid Application Toolkit

A simple API for Grid Applications 		GAT
Menu


next up previous contents
Next: Closing a Connection Up: HTTP Previous: Client Request   Contents

Server Response

In contrast to the conventional emotional fecundity[*] evident in a human's response to their true love's first solicitations, the Urim and Thummin thrown by a server engaging in the protocols of HTTP are cold, calculated, and devoid of all emotion. For example, 

HTTP/1.1 200 OK
Server: Apache/1.3.29 (Darwin)
MIME-version: 1.0
Content-type: text/html
Content-length: 192

<html>
  <head>
    <title>
      Little Black Book
    </title>
  </head>
  <body>
    I would never give my little black book 
    to the likes of your sorry <em>@$$</em>!
  </body>
</html>

The first part of the first line in this server's response indicates the HTTP protocol being used, in this case ``HTTP/1.1''. The second part of the first line is a status code which indicates the status of the response. In this case ``200 OK'' indicates that the request has succeeded. The next line indicates the type of server ``Apache/1.3.29 (Darwin).'' The next line indicates the MIME version the server is using ``1.0''. The following line indicates the type of the returned information ``text/html''. The very next line indicates the length of the response in bytes ``192'', this length does not include all of the header information that we have examined so far. The length is that of the ``payload'' 

<html>
  <head>
    <title>
      Little Black Book
    </title>
  </head>
  <body>
    I would never give my little black book 
    to the likes of your sorry <em>@$$</em>!
  </body>
</html>
As you've seen, finally, after the header meta-data information is complete, the actual payload is presented.

next up previous contents
Next: Closing a Connection Up: HTTP Previous: Client Request   Contents
Andre Merzky 2004-05-13