From: Rainer Jung Date: Fri, 2 Jan 2015 11:57:52 +0000 (+0000) Subject: Xforms. X-Git-Tag: 2.2.30~193 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=46b8b9d4189afa9187f1f3c10427a48db2b420c7;p=thirdparty%2Fapache%2Fhttpd.git Xforms. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1649006 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy_ajp.html.en b/docs/manual/mod/mod_proxy_ajp.html.en index e00ab42b4ec..d5eb7fe3404 100644 --- a/docs/manual/mod/mod_proxy_ajp.html.en +++ b/docs/manual/mod/mod_proxy_ajp.html.en @@ -162,11 +162,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.

@@ -578,9 +574,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

diff --git a/docs/manual/mod/mod_proxy_ajp.xml.ja b/docs/manual/mod/mod_proxy_ajp.xml.ja index 065f678569a..49023e17dbe 100644 --- a/docs/manual/mod/mod_proxy_ajp.xml.ja +++ b/docs/manual/mod/mod_proxy_ajp.xml.ja @@ -1,7 +1,7 @@ - +