diff options
author | Rainer Jung <rjung@apache.org> | 2015-01-02 11:36:45 +0000 |
---|---|---|
committer | Rainer Jung <rjung@apache.org> | 2015-01-02 11:36:45 +0000 |
commit | 567423717e6c4b05074986fb7f97971d8db0ee64 (patch) | |
tree | 5c1b8595fba7715a819e951c160bcb775ad71474 /docs | |
parent | fa1cfae378c950e2d185ed12ef7049f7cadef3d1 (diff) | |
download | httpd-567423717e6c4b05074986fb7f97971d8db0ee64.tar.gz |
PR 48460: Improve/correct mod_proxy_ajp docs.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1649001 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs')
-rw-r--r-- | docs/manual/mod/mod_proxy_ajp.xml | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/docs/manual/mod/mod_proxy_ajp.xml b/docs/manual/mod/mod_proxy_ajp.xml index f358cfb138..6482ab2c81 100644 --- a/docs/manual/mod/mod_proxy_ajp.xml +++ b/docs/manual/mod/mod_proxy_ajp.xml @@ -148,11 +148,7 @@ ProxyPassReverse /apps/foo http://www.example.com/foo <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> @@ -573,9 +569,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> |