PR 48460: Improve/correct mod_proxy_ajp docs.

Backport of r1649001 from trunk
resp. r1649003 from 2.4.x (CTR).

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1649005 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_proxy_ajp.xml b/docs/manual/mod/mod_proxy_ajp.xml
index 5f22c2bc408f9fe572414b9aea3c27f8713e46c9..ee85a96c7c5d6217ad1637a091ed6a6f3ebdb206 100644 (file)
--- a/docs/manual/mod/mod_proxy_ajp.xml
+++ b/docs/manual/mod/mod_proxy_ajp.xml
@@ -146,11 +146,7 @@
 <section id="basppacketstruct"><title>Basic Packet Structure</title>
     <p>There is a bit of an XDR heritage to this protocol, but it differs
     in lots of ways (no 4 byte alignment, for example).</p>
-    <p>Byte order: I am not clear about the endian-ness of the individual
-    bytes.  I'm guessing the bytes are little-endian, because that's what
-    XDR specifies, and I'm guessing that sys/socket library is magically
-    making that so (on the C side).  If anyone with a better knowledge of
-    socket calls can step in, that would be great.</p>
+    <p>AJP13 uses network byte order for all data types.</p>
     <p>There are four data types in the protocol: bytes, booleans,
     integers and strings.</p>
     <dl>
@@ -570,9 +566,9 @@ AJP13_GET_BODY_CHUNK :=
   </section>
   <section><title>End Response</title>
     <p>Signals the end of this request-handling cycle.  If the
-    <code>reuse</code> flag is true <code>(==1)</code>, this TCP connection can
-    now be used to handle new incoming requests.  If <code>reuse</code> is false
-    (anything other than 1 in the actual C code), the connection should
+    <code>reuse</code> flag is true <code>(anything other than 0 in the actual
+    C code)</code>, this TCP connection can now be used to handle new incoming
+    requests.  If <code>reuse</code> is false (==0), the connection should
     be closed.</p>
   </section>
   <section><title>Get Body Chunk</title>