From c829a30eca83fa0615871dfbaccefeee0b80c184 Mon Sep 17 00:00:00 2001 From: Rainer Jung Date: Fri, 2 Jan 2015 11:51:03 +0000 Subject: [PATCH] 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 --- docs/manual/mod/mod_proxy_ajp.xml | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/manual/mod/mod_proxy_ajp.xml b/docs/manual/mod/mod_proxy_ajp.xml index 5f22c2bc408..ee85a96c7c5 100644 --- a/docs/manual/mod/mod_proxy_ajp.xml +++ b/docs/manual/mod/mod_proxy_ajp.xml @@ -146,11 +146,7 @@
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.

@@ -570,9 +566,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 -- 2.47.3