httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From humbed...@apache.org
Subject svn commit: r1371060 - in /httpd/httpd/branches/2.2.x/docs/manual/mod: mod_proxy_ajp.xml mod_proxy_ftp.xml
Date Thu, 09 Aug 2012 07:32:53 GMT
Author: humbedooh
Date: Thu Aug  9 07:32:53 2012
New Revision: 1371060

URL: http://svn.apache.org/viewvc?rev=1371060&view=rev
Log:
typo fixes

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ftp.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml?rev=1371060&r1=1371059&r2=1371060&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml Thu Aug  9 07:32:53 2012
@@ -117,10 +117,10 @@
     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
@@ -136,7 +136,7 @@
     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.
@@ -274,7 +274,7 @@
     <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>
@@ -574,7 +574,7 @@ AJP13_GET_BODY_CHUNK :=
   <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/>

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ftp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ftp.xml?rev=1371060&r1=1371059&r2=1371060&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ftp.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ftp.xml Thu Aug  9 07:32:53 2012
@@ -139,7 +139,7 @@
         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 -->



Mime
View raw message