From: Rainer Jung Date: Fri, 2 Jan 2015 11:36:45 +0000 (+0000) Subject: PR 48460: Improve/correct mod_proxy_ajp docs. X-Git-Tag: 2.5.0-alpha~3575 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=567423717e6c4b05074986fb7f97971d8db0ee64;p=apache 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 --- 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
Basic Packet Structure

There is a bit of an XDR heritage to this protocol, but it differs in lots of ways (no 4 byte alignment, for example).

-

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.

+

AJP13 uses network byte order for all data types.

There are four data types in the protocol: bytes, booleans, integers and strings.

@@ -573,9 +569,9 @@ AJP13_GET_BODY_CHUNK :=
End Response

Signals the end of this request-handling cycle. If the - reuse flag is true (==1), this TCP connection can - now be used to handle new incoming requests. If reuse is false - (anything other than 1 in the actual C code), the connection should + reuse flag is true (anything other than 0 in the actual + C code), this TCP connection can now be used to handle new incoming + requests. If reuse is false (==0), the connection should be closed.

Get Body Chunk