From: Rainer Jung 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. Signals the end of this request-handling cycle. If the
- Basic Packet Structure
@@ -574,9 +570,9 @@ AJP13_GET_BODY_CHUNK :=
End Response
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.html.fr b/docs/manual/mod/mod_proxy_ajp.html.fr
index 0567a733e99..196c797b55c 100644
--- a/docs/manual/mod/mod_proxy_ajp.html.fr
+++ b/docs/manual/mod/mod_proxy_ajp.html.fr
@@ -28,6 +28,8 @@
fr |
ja
Description: | Module de support AJP pour
mod_proxy |
---|---|
Statut: | Extension |