The HTTP protocol is a request/response protocol. This means that a client, such as a web browser, sends a request to the web server in the form of an HTTP request message. This request contains, as part of its' content, a request method, Uniform Resource Identifier (URI), and protocol version followed by a MIME-like message. Uniform Resource Identifiers are simply formatted strings, which identify--via name, location, or any other characteristic--a resource - affectionately known as a URL.

Once this message reaches the server, an attempt is made to satisfy the request. The server responds with a status line, including the message's protocol version and a success or error code and the requested resource. If there are embedded images or objects in the HTML response, the Web browser makes subsequent requests for each embedded object.

The Request object contains information about the current HTTP request. Strictly speaking, the information being passed to you, the server, from the requesting browser.   Prior to using this information, the Active Server Page engine parses the HTTP request and places the information in a series of collections.  As we proceed with our discussion, it will become evident that the entire Request Object is simply a big container for five different collections.  I'll talk more about the anatomy of a collection a little later on, for now review the following table:

In your Active Server Page script, you will use this object to retrieve information about the request such as form variables, query string information, cookies, and certificates.