tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From billbar...@apache.org
Subject cvs commit: jakarta-tomcat-catalina/webapps/docs/config ajp.xml
Date Sun, 03 Jul 2005 00:31:53 GMT
billbarker    2005/07/02 17:31:53

  Modified:    webapps/docs changelog.xml
               webapps/docs/config ajp.xml
  Log:
  Doc changes.
  
  Revision  Changes    Path
  1.320     +3 -0      jakarta-tomcat-catalina/webapps/docs/changelog.xml
  
  Index: changelog.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v
  retrieving revision 1.319
  retrieving revision 1.320
  diff -u -r1.319 -r1.320
  --- changelog.xml	30 Jun 2005 13:08:14 -0000	1.319
  +++ changelog.xml	3 Jul 2005 00:31:53 -0000	1.320
  @@ -205,6 +205,9 @@
         <fix>
           Fix connector initialisation so sslProtocol is not required for SSL. (markt)
         </fix>
  +      <add>
  +        Add bufferSize option to the AJP/1.3 Java connector to control output buffering.
(billbarker)
  +      </add>
        </changelog>
     </subsection>
   
  
  
  
  1.19      +11 -5     jakarta-tomcat-catalina/webapps/docs/config/ajp.xml
  
  Index: ajp.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/config/ajp.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- ajp.xml	3 Jul 2005 00:26:51 -0000	1.18
  +++ ajp.xml	3 Jul 2005 00:31:53 -0000	1.19
  @@ -86,14 +86,14 @@
         the container during FORM or CLIENT-CERT authentication. For both types
         of authentication, the POST will be saved/buffered before the user is
         authenticated. For CLIENT-CERT authentication, the POST is buffered for
  -      the duration of
 the SSL handshake and the buffer emptied when the request
  -      is processed. For FORM authentication the POST is
 saved whilst the user
  +      the duration of the SSL handshake and the buffer emptied when the request
  +      is processed. For FORM authentication the POST is saved whilst the user
         is re-directed to the login form and is retained until the user
         successfully authenticates or the session associated with the
         authentication request expires. The limit can be disabled by setting this
  -      attribute to -1. Setting the attribute to
 zero will disable the saving of
  -      POST data during authentication
. If not
 specified, this attribute is set
  -      to
 4096 (4 kilobytes).</p>
  +      attribute to -1. Setting the attribute to zero will disable the saving of
  +      POST data during authentication. If not specified, this attribute is set
  +      to 4096 (4 kilobytes).</p>
       </attribute>
   
       <attribute name="protocol" required="false">
  @@ -207,6 +207,12 @@
         value is 10.</p>
       </attribute>
   
  +    <attribute name="bufferSize" required="false">
  +      <p>The size of the output buffer to use.  If less than or equal to zero,
  +         then output buffering is disabled.  The default value is -1
  +         (i.e. buffering disabled)</p>
  +    </attribute>
  +
       <attribute name="connectionTimeout" required="false">
         <p>The number of milliseconds this <strong>Connector</strong> will
wait,
         after accepting a connection, for the request URI line to be
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message