httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48460] New: mod_proxy_ajp document has three misleading portions
Date Wed, 30 Dec 2009 08:38:30 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48460

           Summary: mod_proxy_ajp document has three misleading portions
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Documentation
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: inoue@ariel-networks.com


I found three misleading portions in mod_proxy_ajp document.
It looks they are derived from
http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html.


1. about byte-order (endian-ness)

Excerpted from the original:

    <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>

AJP uses big-endian (I have checked mod_proxy_ajp source code).
XDR also uses big-endian. See http://www.faqs.org/rfcs/rfc1014.html.
socket library function such as htons(3) also uses big-endian(= network byte
order).

I suggest that we remove the portion above, and modify the following portion
which describes 'integer'.

    <dt><strong>Integer</strong></dt>
      <dd>A number in the range of <code>0 to 2^16 (32768)</code>.  Stored
in
      2 bytes with the high-order byte first.</dd>

to

    <dt><strong>Integer</strong></dt>
      <dd>A number in the range of <code>0 to 2^16 (32768)</code>.  Stored
in
      2 bytes with the high-order byte first, which is known as
big-endian.</dd>


2. a wrong number

Excerpted from the original:

    <p>This works on the assumption that no header names will have length
    greater than <code>0x9999 (==0xA000 - 1)</code>, which is perfectly
    reasonable, though somewhat arbitrary.</p>

This should be as follows,

<code>0x9FFF (==0xA000 - 1)</code>


3. description about boolean

Excerpted from the original:

  <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
    be closed.</p>
  </section>

This should be as follows,

true <code>(anything other than 0 in the actual C code)</code>
false <code>(==0)</code>

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message