typo fixes

    the connection can be in one of the following states:</p>

    <ul>

    <li> Idle <br/> No request is being handled over this connection. </li>

    <li> Assigned <br/> The connecton is handling a specific request.</li>

    <li> Assigned <br/> The connection is handling a specific request.</li>

    </ul>

    <p>Once a connection is assigned to handle a particular request, the basic

    request informaton (e.g. HTTP headers, etc) is sent over the connection in

    request information (e.g. HTTP headers, etc) is sent over the connection in

    a highly condensed form (e.g. common strings are encoded as integers).

    Details of that format are below in Request Packet Structure. If there is a

    body to the request <code>(content-length > 0)</code>, that is sent in a

    been transferred yet.  This is necessary because the packets have a fixed

    maximum size and arbitrary amounts of data can be included the body of a

    request (for uploaded files, for example).  (Note: this is unrelated to

    HTTP chunked tranfer).</li>

    HTTP chunked transfer).</li>

    <li>END_RESPONSE <br/> Finish the request-handling cycle.</li>

    </ul>

    <p>Each message is accompanied by a differently formatted packet of data.

    <p>To ensure some basic security, the container will only actually do the

    <code>Shutdown</code> if the request comes from the same machine on which

    it's hosted.</p>

    <p>The first <code>Data</code> packet is send immediatly after the

    <p>The first <code>Data</code> packet is send immediately after the

    <code>Forward Request</code> by the web server.</p>

    <p>The servlet container can send the following types of messages to the

    webserver:</p>

  <section><title>Get Body Chunk</title>

    <p>The container asks for more data from the request (If the body was

    too large to fit in the first packet sent over or when the request is

    chuncked). The server will send a body packet back with an amount of data

    chunked). The server will send a body packet back with an amount of data

    which is the minimum of the <code>request_length</code>, the maximum send

    body size <code>(8186 (8 Kbytes - 6))</code>, and the number of bytes

    actually left to send from the request body.<br/>

        a base64-encoded cleartext string, and between the Apache proxy and the

        FTP server as plaintext. You should therefore think twice before

        accessing your FTP server via HTTP (or before accessing your personal

        files via FTP at all!) When using unsecure channels, an eavesdropper

        files via FTP at all!) When using insecure channels, an eavesdropper

        might intercept your password on its way.</p>

      </note>

    </section> <!-- /ftppass -->