Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8DA217396 for ; Tue, 1 Sep 2015 14:23:30 +0000 (UTC) Received: (qmail 76051 invoked by uid 500); 1 Sep 2015 14:23:20 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 75980 invoked by uid 500); 1 Sep 2015 14:23:20 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 75970 invoked by uid 99); 1 Sep 2015 14:23:20 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Sep 2015 14:23:20 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id 94395AC003E for ; Tue, 1 Sep 2015 14:23:20 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1700565 - in /tomcat/jk/trunk/xdocs/ajp: ajpv13a.xml ajpv13ext.xml Date: Tue, 01 Sep 2015 14:23:20 -0000 To: dev@tomcat.apache.org From: rjung@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150901142320.94395AC003E@hades.apache.org> Author: rjung Date: Tue Sep 1 14:23:20 2015 New Revision: 1700565 URL: http://svn.apache.org/r1700565 Log: Fix some typos etc. Content essentially unchanged. Modified: tomcat/jk/trunk/xdocs/ajp/ajpv13a.xml tomcat/jk/trunk/xdocs/ajp/ajpv13ext.xml Modified: tomcat/jk/trunk/xdocs/ajp/ajpv13a.xml URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/ajp/ajpv13a.xml?rev=1700565&r1=1700564&r2=1700565&view=diff ============================================================================== --- tomcat/jk/trunk/xdocs/ajp/ajpv13a.xml (original) +++ tomcat/jk/trunk/xdocs/ajp/ajpv13a.xml Tue Sep 1 14:23:20 2015 @@ -552,7 +552,7 @@ additional methods, even if they are not

The route, as I understand it, is used to support sticky sessions -- associating a user's session with a particular Tomcat instance - in the presence of multiple, load-balancing servers. I don't know the + in the presence of multiple, load balancing servers. I don't know the details.

Beyond this list of basic attributes, any number of other attributes can Modified: tomcat/jk/trunk/xdocs/ajp/ajpv13ext.xml URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/ajp/ajpv13ext.xml?rev=1700565&r1=1700564&r2=1700565&view=diff ============================================================================== --- tomcat/jk/trunk/xdocs/ajp/ajpv13ext.xml (original) +++ tomcat/jk/trunk/xdocs/ajp/ajpv13ext.xml Tue Sep 1 14:23:20 2015 @@ -52,12 +52,12 @@ send to servlet engine many info from we

-But ajp13 lacks support for : +But ajp13 lacks support for:

security between web server and servlet engine. - Anybody can connect to an ajp13 port (no login mecanism used) + Anybody can connect to an ajp13 port (no login mechanism used) You could connect, for example with telnet, and keep the remote thread up by not sending any data (no timeout in connection)

-The secret key will be set by a new propertie in -workers.properties : secretkey +The secret key will be set by a new property in +workers.properties: secretkey worker.ajp13.port=8009 worker.ajp13.host=localhost @@ -233,7 +233,7 @@ worker.ajp13.secretkey=myverysecretkey

-AJP13 miss a functionnality of AJP12, which is shutdown command. +AJP13 miss a functionality of AJP12, which is shutdown command. A logout will tell servlet engine to shutdown itself. +--------------+----------------------------+ @@ -281,10 +281,10 @@ passed to their servlet engine. To reduce the network traffic, the web-servlet will send a table to describing the external vars in a shorter fashion. -We'll use there a functionnality allready present in AJP13, -attributes list : +We'll use there a functionality allready present in AJP13, +attributes list: -In the AJP13, we've got : +In the AJP13, we've got: AJP13_FORWARD_REQUEST := @@ -323,7 +323,7 @@ network traffic. +-------------------+---------------------------+-------------------------------+----+ -ie : +ie: JkExtVars S1 SSL_CLIENT_V_START javax.servlet.request.ssl_start_cert_date @@ -347,7 +347,7 @@ containing S1, S2, S3 and attributes val 2001/01/03, 2002/01/03, 0123AFE56. This example showed the use of extended SSL vars but -any 'personnal' web-server vars like custom authentification +any 'personal' web-server vars like custom authentification vars could be reused in the servlet engine. The cost will be only some more bytes in the AJP traffic. @@ -366,7 +366,7 @@ ES is an empty CString.

- +

Just after the LOGON PHASE, the web server will ask for the list of contexts and URLs/URIs handled by the servlet engine. @@ -378,13 +378,13 @@ This mode will be activated by a new dir ie: JkAutoMount examples myworker1 /examples/ If we want to get ALL the contexts handled by the servlet engine, willcard -could be used : +could be used: ie: JkAutoMount * myworker1 * A servlet engine could have many contexts, /examples, /admin, /test. We may want to use only some contexts for a given worker. It was -done previously, in apache HTTP server for example, by setting by +done previously, in Apache HTTP Server for example, by setting by hand the JkMount accordingly in each [virtual] area of Apache. If you web-server support virtual hosting, we'll forward also that @@ -393,7 +393,7 @@ that virtual host. In that case the servlet engine will only return the URL/URI matching these particular virtual server (defined in server.xml). This feature will help ISP and big sites which mutualize large farm -of Tomcat in load-balancing configuration. +of Tomcat in load balancing configuration. +-----------------+-------------------+----------+----------+----+ @@ -430,7 +430,7 @@ In that case the servlet engine will sen

- +

Context update are messages caming from the servlet engine each time a context is desactivated/reactivated. The update will be in use when the directive JkUpdateMount. @@ -544,7 +544,7 @@ We could use a buffering scheme but what for upload operations with more than 8ko of datas ? The hack in the AJP13 protocol is to add some bytes to read after the end of the -service : +service: EXAMPLE OF DISCUSSION BETWEEN WEB SERVER AND SERVLET ENGINE @@ -566,7 +566,7 @@ More at that time the web server could a to read. And that datas could be CONTEXT Updates. This will avoid the web server sending a request to a -desactivated context. In that case, if the load-balancing is used, +desactivated context. In that case, if the load balancing is used, it will search for another servlet engine to handle the request. And that feature will help ISP and big sites with farm of tomcat, --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org