Author: markt
Date: Mon Aug 17 10:48:16 2015
New Revision: 1696233
URL: http://svn.apache.org/r1696233
Log:
Update jk-docs for 1.2.41 release
Added:
tomcat/site/trunk/docs/connectors-doc/common_howto/
tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/proxy.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/quick.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/timeouts.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/workers.html
(with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/proxy.html (with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/quick.html (with props)
tomcat/site/trunk/docs/connectors-doc/common_howto/timeouts.html (with
props)
tomcat/site/trunk/docs/connectors-doc/common_howto/workers.html (with
props)
tomcat/site/trunk/docs/connectors-doc/news/20150101.html (with props)
tomcat/site/trunk/docs/connectors-doc/news/printer/20150101.html (with
props)
Removed:
tomcat/site/trunk/docs/connectors-doc/generic_howto/
Modified:
tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13a.html
tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13ext.html
tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13a.html
tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13ext.html
tomcat/site/trunk/docs/connectors-doc/index.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/changelog.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/doccontrib.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/faq.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/jkstatustasks.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/printer/changelog.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/printer/doccontrib.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/printer/faq.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/printer/jkstatustasks.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/printer/reporttools.html
tomcat/site/trunk/docs/connectors-doc/miscellaneous/reporttools.html
tomcat/site/trunk/docs/connectors-doc/news/20041100.html
tomcat/site/trunk/docs/connectors-doc/news/20050101.html
tomcat/site/trunk/docs/connectors-doc/news/20060101.html
tomcat/site/trunk/docs/connectors-doc/news/20070301.html
tomcat/site/trunk/docs/connectors-doc/news/20081001.html
tomcat/site/trunk/docs/connectors-doc/news/20090301.html
tomcat/site/trunk/docs/connectors-doc/news/20100101.html
tomcat/site/trunk/docs/connectors-doc/news/20110701.html
tomcat/site/trunk/docs/connectors-doc/news/20120301.html
tomcat/site/trunk/docs/connectors-doc/news/20140201.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20041100.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20050101.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20060101.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20070301.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20081001.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20090301.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20100101.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20110701.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20120301.html
tomcat/site/trunk/docs/connectors-doc/news/printer/20140201.html
tomcat/site/trunk/docs/connectors-doc/printer/index.html
tomcat/site/trunk/docs/connectors-doc/reference/apache.html
tomcat/site/trunk/docs/connectors-doc/reference/iis.html
tomcat/site/trunk/docs/connectors-doc/reference/printer/apache.html
tomcat/site/trunk/docs/connectors-doc/reference/printer/iis.html
tomcat/site/trunk/docs/connectors-doc/reference/printer/status.html
tomcat/site/trunk/docs/connectors-doc/reference/printer/uriworkermap.html
tomcat/site/trunk/docs/connectors-doc/reference/printer/workers.html
tomcat/site/trunk/docs/connectors-doc/reference/status.html
tomcat/site/trunk/docs/connectors-doc/reference/uriworkermap.html
tomcat/site/trunk/docs/connectors-doc/reference/workers.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/apache.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/iis.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/nes.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/printer/apache.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/printer/iis.html
tomcat/site/trunk/docs/connectors-doc/webserver_howto/printer/nes.html
Modified: tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13a.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13a.html?rev=1696233&r1=1696232&r2=1696233&view=diff
==============================================================================
--- tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13a.html (original)
+++ tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13a.html Mon Aug 17 10:48:16
2015
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connector - AJP Protocol Reference
- AJPv13</title><meta name="author" value="dan...@shore.net"><meta name="email"
value="dan...@shore.net"><meta name="author" value="Jean-Frederic Clere"><meta
name="email" value="jfrederic.cl...@fujitsu-siemens.com"><link
href="../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../images/tomcat.gif" align="left"
alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--LEFT
SIDE NAVIGATION--><td width="20%" valign="top"
nowrap="true"><p><strong>Links</strong></p><ul><li><a href="../index.html">Docs
Home</a></li></ul><p><strong>Reference Guide</strong></p><ul><li><a
href="../reference/workers.html">workers.properties</a></li><li><a
href="../reference/uriworkermap.html">uriworkermap.properties</a></li><li><a
href="../reference/status.html">Status Worker</a></li><li><a
href="../reference/apache.html">Apache HTTP Server</a></li><li><a
href="../reference/iis.html">IIS</a></li></ul><p><strong>Generic
HowTo</strong></p><ul><li><a href="../generic_howto/quick.html">For the
impatient</a></li><li><a href="../generic_howto/workers.html">All about
workers</a></li><li><a
href="../generic_howto/timeouts.html">Timeouts</a></li><li><a
href="../generic_howto/loadbalancers.html">Load Balancing</a></li><li><a
href="../generic_howto/proxy.html">Reverse
Proxy</a></li></ul><p><strong>Webserver HowTo</strong></p><ul><li><a
href="../webserver_howto/apache.html">Apache HTTP S
erver</a></li><li><a href="../webserver_howto/iis.html">IIS</a></li><li><a
href="../webserver_howto/nes.html">Netscape/SunOne/Sun</a></li></ul><p><strong>AJP
Protocol Reference</strong></p><ul><li><a
href="../ajp/ajpv13a.html">AJPv13</a></li><li><a
href="../ajp/ajpv13ext.html">AJPv13 Extension
Proposal</a></li></ul><p><strong>Miscellaneous
Documentation</strong></p><ul><li><a
href="../miscellaneous/faq.html">Frequently asked questions</a></li><li><a
href="../miscellaneous/changelog.html">Changelog</a></li><li><a
href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Tomcat+Connectors&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc
2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Current
Tomcat Connectors bugs</a></li><li><a
href="../miscellaneous/doccontrib.html">Contribute documentation</a></li><li><a
href="../miscellaneous/jkstatustasks.html">JK Status Ant Tasks</a></li><li><a
href="../miscellaneous/reporttools.html">Reporting Tools</a></li><li><a
href="http://tomcat.apache.org/connectors-doc-archive/jk2/index.html";>Old
JK/JK2 documentation</a></li></ul><p><strong>News</strong></p><ul><li><a
href="../news/20140201.html">2014</a></li><li><a
href="../news/20120301.html">2012</a></li><li><a
href="../news/20110701.html">2011</a></li><li><a
href="../news/20100101.html">2010</a></li><li><a
href="../news/20090301.html">2009</a></li><li><a
href="../news/20081001.html">2008</a></li><li><a href="../news/20070301.html">
2007</a></li><li><a href="../news/20060101.html">2006</a></li><li><a
href="../news/20050101.html">2005</a></li><li><a
href="../news/20041100.html">2004</a></li></ul></td><!--RIGHT SIDE MAIN
BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connector - AJP Protocol Reference</h1><h2>AJPv13</h2></td><td align="right"
valign="top" nowrap="true"><small><a href="printer/ajpv13a.html"><img
src="../images/printer.gif" border="0" alt="Printer Friendly
Version"><br>print-friendly<br>version
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - AJP Protocol
Reference - AJPv13</title><meta name="author" value="dan...@shore.net"><meta
name="email" value="dan...@shore.net"><meta name="author" value="Jean-Frederic
Clere"><meta name="email" value="jfrederic.cl...@fujitsu-siemens.com"><link
href="../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../images/tomcat.gif" align="left"
alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--LEF
T SIDE NAVIGATION--><td width="20%" valign="top"
nowrap="true"><p><strong>Links</strong></p><ul><li><a href="../index.html">Docs
Home</a></li></ul><p><strong>Common HowTo</strong></p><ul><li><a
href="../common_howto/quick.html">For the impatient</a></li><li><a
href="../common_howto/workers.html">All about workers</a></li><li><a
href="../common_howto/timeouts.html">Timeouts</a></li><li><a
href="../common_howto/loadbalancers.html">Load Balancing</a></li><li><a
href="../common_howto/proxy.html">Reverse
Proxy</a></li></ul><p><strong>Webserver HowTo</strong></p><ul><li><a
href="../webserver_howto/apache.html">Apache HTTP Server</a></li><li><a
href="../webserver_howto/iis.html">IIS</a></li><li><a
href="../webserver_howto/nes.html">Netscape/SunOne/Sun</a></li></ul><p><strong>Reference
Guide</strong></p><ul><li><a
href="../reference/workers.html">workers.properties</a></li><li><a
href="../reference/uriworkermap.html">uriworkermap.properties</a></li><li><a
href="../reference/status.html">Sta
tus Worker</a></li><li><a href="../reference/apache.html">Apache HTTP
Server</a></li><li><a
href="../reference/iis.html">IIS</a></li></ul><p><strong>AJP Protocol
Reference</strong></p><ul><li><a
href="../ajp/ajpv13a.html">AJPv13</a></li><li><a
href="../ajp/ajpv13ext.html">AJPv13 Extension
Proposal</a></li></ul><p><strong>Miscellaneous
Documentation</strong></p><ul><li><a
href="../miscellaneous/faq.html">Frequently asked questions</a></li><li><a
href="../miscellaneous/changelog.html">Changelog</a></li><li><a
href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Tomcat+Connectors&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&a
mp;emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Current
Tomcat Connectors bugs</a></li><li><a
href="../miscellaneous/doccontrib.html">Contribute documentation</a></li><li><a
href="../miscellaneous/jkstatustasks.html">JK Status Ant Tasks</a></li><li><a
href="../miscellaneous/reporttools.html">Reporting Tools</a></li><li><a
href="http://tomcat.apache.org/connectors-doc-archive/jk2/index.html";>Old
JK/JK2 documentation</a></li></ul><p><strong>News</strong></p><ul><li><a
href="../news/20140201.html">2014</a></li><li><a
href="../news/20120301.html">2012</a></li><li><a
href="../news/20110701.html">2011</a></li><li><a
href="../news/20100101.html">2010</a></li><li><a
href="../news/20090301.html">2009</a></li><li><a
href="../news/20081001.html">2008</a></li><li><a
href="../news/20070301.html">2007<
/a></li><li><a href="../news/20060101.html">2006</a></li><li><a
href="../news/20050101.html">2005</a></li><li><a
href="../news/20041100.html">2004</a></li></ul></td><!--RIGHT SIDE MAIN
BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connectors - AJP Protocol Reference</h1><h2>AJPv13</h2></td><td align="right"
valign="top" nowrap="true"><small><a href="printer/ajpv13a.html"><img
src="../images/printer.gif" border="0" alt="Printer Friendly
Version"><br>print-friendly<br>version
</a></small></td></tr></table><table border="0"
cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
color="#ffffff" face="arial,helvetica.sanserif"><a
name="Intro"><strong>Intro</strong></a></font></td></tr><tr><td><blockquote>
<p>
@@ -108,13 +108,11 @@ Response Packet Structures below for det
<p>
There is a bit of an XDR heritage to this protocol, but it differs in
lots of ways (no 4 byte alignment, for example).
-</p><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><p>
+</p>
+<p>
+ AJP13 uses network byte order for all data types.
+</p>
+<p>
There are four data types in the protocol: bytes, booleans, integers and
strings.
@@ -450,7 +448,7 @@ additional methods, even if they are not
two-byte integer is the length of a string, which is then read in.
</p><p>
This works on the assumption that no header names will have length
- greater than 0x9999 (==0xA000 - 1), which is perfectly reasonable, though
+ greater than 0x9FFF (==0xA000 - 1), which is perfectly reasonable, though
somewhat arbitrary. (If you, like me, started to think about the cookie
spec here, and about how long headers can get, fear not -- this limit is
on header <b>names</b> not header <b>values</b>. It seems unlikely that
@@ -470,7 +468,7 @@ additional methods, even if they are not
The attributes prefixed with a <b class="code">?</b>
(e.g. <b class="code">?context</b>) are all optional. For each, there is a
single byte code to indicate the type of attribute, and then a string to
- give its value. They can be sent in any order (thogh the C code always
+ give its value. They can be sent in any order (though the C code always
sends them in the order listed below). A special terminating code is
sent to signal the end of the list of optional attributes. The list of
byte codes is:
@@ -612,9 +610,10 @@ Details:
<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="End Response"><strong>End
Response</strong></a></font></td></tr><tr><td><blockquote>
<p>
Signals the end of this request-handling cycle. If the
- <b class="code">reuse</b> flag is true (==1), this TCP connection can now be
used to
- handle new incoming requests. If <b class="code">reuse</b> is false
(anything
- other than 1 in the actual C code), the connection should be closed.
+ <b class="code">reuse</b> 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 <b class="code">reuse</b> is false (==0), the connection
+ should be closed.
</p>
</blockquote></td></tr></table>
@@ -650,5 +649,5 @@ of the connection between the web server
me as potentially dangerous.</p>
</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
- Copyright © 1999-2014, Apache Software Foundation
+ Copyright © 1999-2015, Apache Software Foundation
</em></font></div></td></tr></table></body></html>
\ No newline at end of file
Modified: tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13ext.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13ext.html?rev=1696233&r1=1696232&r2=1696233&view=diff
==============================================================================
--- tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13ext.html (original)
+++ tomcat/site/trunk/docs/connectors-doc/ajp/ajpv13ext.html Mon Aug 17
10:48:16 2015
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connector - AJP Protocol Reference
- AJPv13 extensions Proposal</title><meta name="author" value="Henri
Gomez"><meta name="email" value="hgo...@apache.org"><link href="../style.css"
type="text/css" rel="stylesheet"></head><body bgcolor="#ffffff" text="#000000"
link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%"
cellspacing="4"><!--PAGE HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../images/tomcat.gif" align="left"
alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--LEFT SIDE NAVIGATION--><td
width="20%" valign="top" nowrap="true"><p><strong>Links</strong></p><ul>
<li><a href="../index.html">Docs Home</a></li></ul><p><strong>Reference
Guide</strong></p><ul><li><a
href="../reference/workers.html">workers.properties</a></li><li><a
href="../reference/uriworkermap.html">uriworkermap.properties</a></li><li><a
href="../reference/status.html">Status Worker</a></li><li><a
href="../reference/apache.html">Apache HTTP Server</a></li><li><a
href="../reference/iis.html">IIS</a></li></ul><p><strong>Generic
HowTo</strong></p><ul><li><a href="../generic_howto/quick.html">For the
impatient</a></li><li><a href="../generic_howto/workers.html">All about
workers</a></li><li><a
href="../generic_howto/timeouts.html">Timeouts</a></li><li><a
href="../generic_howto/loadbalancers.html">Load Balancing</a></li><li><a
href="../generic_howto/proxy.html">Reverse
Proxy</a></li></ul><p><strong>Webserver HowTo</strong></p><ul><li><a
href="../webserver_howto/apache.html">Apache HTTP Server</a></li><li><a
href="../webserver_howto/iis.html">IIS</a></li><li><a href="../webserver_h
owto/nes.html">Netscape/SunOne/Sun</a></li></ul><p><strong>AJP Protocol
Reference</strong></p><ul><li><a
href="../ajp/ajpv13a.html">AJPv13</a></li><li><a
href="../ajp/ajpv13ext.html">AJPv13 Extension
Proposal</a></li></ul><p><strong>Miscellaneous
Documentation</strong></p><ul><li><a
href="../miscellaneous/faq.html">Frequently asked questions</a></li><li><a
href="../miscellaneous/changelog.html">Changelog</a></li><li><a
href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Tomcat+Connectors&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfie
ldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Current
Tomcat Connectors bugs</a></li><li><a
href="../miscellaneous/doccontrib.html">Contribute documentation</a></li><li><a
href="../miscellaneous/jkstatustasks.html">JK Status Ant Tasks</a></li><li><a
href="../miscellaneous/reporttools.html">Reporting Tools</a></li><li><a
href="http://tomcat.apache.org/connectors-doc-archive/jk2/index.html";>Old
JK/JK2 documentation</a></li></ul><p><strong>News</strong></p><ul><li><a
href="../news/20140201.html">2014</a></li><li><a
href="../news/20120301.html">2012</a></li><li><a
href="../news/20110701.html">2011</a></li><li><a
href="../news/20100101.html">2010</a></li><li><a
href="../news/20090301.html">2009</a></li><li><a
href="../news/20081001.html">2008</a></li><li><a
href="../news/20070301.html">2007</a></li><li><a
href="../news/20060101.html">2006</a></li><li><a href="../news/20050101.htm
l">2005</a></li><li><a
href="../news/20041100.html">2004</a></li></ul></td><!--RIGHT SIDE MAIN
BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connector - AJP Protocol Reference</h1><h2>AJPv13 extensions
Proposal</h2></td><td align="right" valign="top" nowrap="true"><small><a
href="printer/ajpv13ext.html"><img src="../images/printer.gif" border="0"
alt="Printer Friendly Version"><br>print-friendly<br>version
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - AJP Protocol
Reference - AJPv13 extensions Proposal</title><meta name="author" value="Henri
Gomez"><meta name="email" value="hgo...@apache.org"><link href="../style.css"
type="text/css" rel="stylesheet"></head><body bgcolor="#ffffff" text="#000000"
link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%"
cellspacing="4"><!--PAGE HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../images/tomcat.gif" align="left"
alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--LEFT SIDE NAVIGATION--><td
width="20%" valign="top" nowrap="true"><p><strong>Links</strong></p><ul
><li><a href="../index.html">Docs Home</a></li></ul><p><strong>Common
>HowTo</strong></p><ul><li><a href="../common_howto/quick.html">For the
>impatient</a></li><li><a href="../common_howto/workers.html">All about
>workers</a></li><li><a
>href="../common_howto/timeouts.html">Timeouts</a></li><li><a
>href="../common_howto/loadbalancers.html">Load Balancing</a></li><li><a
>href="../common_howto/proxy.html">Reverse
>Proxy</a></li></ul><p><strong>Webserver HowTo</strong></p><ul><li><a
>href="../webserver_howto/apache.html">Apache HTTP Server</a></li><li><a
>href="../webserver_howto/iis.html">IIS</a></li><li><a
>href="../webserver_howto/nes.html">Netscape/SunOne/Sun</a></li></ul><p><strong>Reference
> Guide</strong></p><ul><li><a
>href="../reference/workers.html">workers.properties</a></li><li><a
>href="../reference/uriworkermap.html">uriworkermap.properties</a></li><li><a
>href="../reference/status.html">Status Worker</a></li><li><a
>href="../reference/apache.html">Apache HTTP Server</a></li><li><a hre
f="../reference/iis.html">IIS</a></li></ul><p><strong>AJP Protocol
Reference</strong></p><ul><li><a
href="../ajp/ajpv13a.html">AJPv13</a></li><li><a
href="../ajp/ajpv13ext.html">AJPv13 Extension
Proposal</a></li></ul><p><strong>Miscellaneous
Documentation</strong></p><ul><li><a
href="../miscellaneous/faq.html">Frequently asked questions</a></li><li><a
href="../miscellaneous/changelog.html">Changelog</a></li><li><a
href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Tomcat+Connectors&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfro
m=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Current
Tomcat Connectors bugs</a></li><li><a
href="../miscellaneous/doccontrib.html">Contribute documentation</a></li><li><a
href="../miscellaneous/jkstatustasks.html">JK Status Ant Tasks</a></li><li><a
href="../miscellaneous/reporttools.html">Reporting Tools</a></li><li><a
href="http://tomcat.apache.org/connectors-doc-archive/jk2/index.html";>Old
JK/JK2 documentation</a></li></ul><p><strong>News</strong></p><ul><li><a
href="../news/20140201.html">2014</a></li><li><a
href="../news/20120301.html">2012</a></li><li><a
href="../news/20110701.html">2011</a></li><li><a
href="../news/20100101.html">2010</a></li><li><a
href="../news/20090301.html">2009</a></li><li><a
href="../news/20081001.html">2008</a></li><li><a
href="../news/20070301.html">2007</a></li><li><a
href="../news/20060101.html">2006</a></li><li><a href="../news/20050101.html">20
05</a></li><li><a
href="../news/20041100.html">2004</a></li></ul></td><!--RIGHT SIDE MAIN
BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connectors - AJP Protocol Reference</h1><h2>AJPv13 extensions
Proposal</h2></td><td align="right" valign="top" nowrap="true"><small><a
href="printer/ajpv13ext.html"><img src="../images/printer.gif" border="0"
alt="Printer Friendly Version"><br>print-friendly<br>version
</a></small></td></tr></table><table border="0"
cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
color="#ffffff" face="arial,helvetica.sanserif"><a
name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
<p>
This document is a proposal of evolution of the current
@@ -134,7 +134,7 @@ run-time (up/down), level of SSL env var
level supported (level1/level2/level3...)
The Web server info will contain web server info and
-connector name (ie Apache 1.3.26 + mod_ssl 2.8.8 + mod_jk 1.2.1 + mod_perl
1.25).
+connector name (ie Apache 1.3.26 + mod_ssl 2.8.8 + mod_jk 1.2.41 + mod_perl
1.25).
The servlet engine will mask the negociation mask with it's own
mask (what it can do) and return it when loggin is accepted.
@@ -650,5 +650,5 @@ All others flags must be set to 0 since
</blockquote></td></tr></table>
</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
- Copyright © 1999-2014, Apache Software Foundation
+ Copyright © 1999-2015, Apache Software Foundation
</em></font></div></td></tr></table></body></html>
\ No newline at end of file
Modified: tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13a.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13a.html?rev=1696233&r1=1696232&r2=1696233&view=diff
==============================================================================
--- tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13a.html (original)
+++ tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13a.html Mon Aug 17
10:48:16 2015
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connector - AJP Protocol Reference
- AJPv13</title><meta name="author" value="dan...@shore.net"><meta name="email"
value="dan...@shore.net"><meta name="author" value="Jean-Frederic Clere"><meta
name="email" value="jfrederic.cl...@fujitsu-siemens.com"><link
href="../../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../../images/tomcat.gif"
align="left" alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!
--RIGHT SIDE MAIN BODY--><td width="80%" valign="top" align="left"><table
border="0" width="100%" cellspacing="4"><tr><td align="left"
valign="top"><h1>The Apache Tomcat Connector - AJP Protocol
Reference</h1><h2>AJPv13</h2></td><td align="right" valign="top"
nowrap="true"><img src="../../images/void.gif" width="1" height="1" vspace="0"
hspace="0" border="0" alt=" "></td></tr></table><table border="0"
cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
color="#ffffff" face="arial,helvetica.sanserif"><a
name="Intro"><strong>Intro</strong></a></font></td></tr><tr><td><blockquote>
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - AJP Protocol
Reference - AJPv13</title><meta name="author" value="dan...@shore.net"><meta
name="email" value="dan...@shore.net"><meta name="author" value="Jean-Frederic
Clere"><meta name="email" value="jfrederic.cl...@fujitsu-siemens.com"><link
href="../../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../../images/tomcat.gif"
align="left" alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><
!--RIGHT SIDE MAIN BODY--><td width="80%" valign="top" align="left"><table
border="0" width="100%" cellspacing="4"><tr><td align="left"
valign="top"><h1>The Apache Tomcat Connectors - AJP Protocol
Reference</h1><h2>AJPv13</h2></td><td align="right" valign="top"
nowrap="true"><img src="../../images/void.gif" width="1" height="1" vspace="0"
hspace="0" border="0" alt=" "></td></tr></table><table border="0"
cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
color="#ffffff" face="arial,helvetica.sanserif"><a
name="Intro"><strong>Intro</strong></a></font></td></tr><tr><td><blockquote>
<p>
The original document was written by
@@ -107,13 +107,11 @@ Response Packet Structures below for det
<p>
There is a bit of an XDR heritage to this protocol, but it differs in
lots of ways (no 4 byte alignment, for example).
-</p><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><p>
+</p>
+<p>
+ AJP13 uses network byte order for all data types.
+</p>
+<p>
There are four data types in the protocol: bytes, booleans, integers and
strings.
@@ -449,7 +447,7 @@ additional methods, even if they are not
two-byte integer is the length of a string, which is then read in.
</p><p>
This works on the assumption that no header names will have length
- greater than 0x9999 (==0xA000 - 1), which is perfectly reasonable, though
+ greater than 0x9FFF (==0xA000 - 1), which is perfectly reasonable, though
somewhat arbitrary. (If you, like me, started to think about the cookie
spec here, and about how long headers can get, fear not -- this limit is
on header <b>names</b> not header <b>values</b>. It seems unlikely that
@@ -469,7 +467,7 @@ additional methods, even if they are not
The attributes prefixed with a <b class="code">?</b>
(e.g. <b class="code">?context</b>) are all optional. For each, there is a
single byte code to indicate the type of attribute, and then a string to
- give its value. They can be sent in any order (thogh the C code always
+ give its value. They can be sent in any order (though the C code always
sends them in the order listed below). A special terminating code is
sent to signal the end of the list of optional attributes. The list of
byte codes is:
@@ -611,9 +609,10 @@ Details:
<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="End Response"><strong>End
Response</strong></a></font></td></tr><tr><td><blockquote>
<p>
Signals the end of this request-handling cycle. If the
- <b class="code">reuse</b> flag is true (==1), this TCP connection can now be
used to
- handle new incoming requests. If <b class="code">reuse</b> is false
(anything
- other than 1 in the actual C code), the connection should be closed.
+ <b class="code">reuse</b> 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 <b class="code">reuse</b> is false (==0), the connection
+ should be closed.
</p>
</blockquote></td></tr></table>
@@ -649,5 +648,5 @@ of the connection between the web server
me as potentially dangerous.</p>
</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
- Copyright © 1999-2014, Apache Software Foundation
+ Copyright © 1999-2015, Apache Software Foundation
</em></font></div></td></tr></table></body></html>
\ No newline at end of file
Modified: tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13ext.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13ext.html?rev=1696233&r1=1696232&r2=1696233&view=diff
==============================================================================
--- tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13ext.html (original)
+++ tomcat/site/trunk/docs/connectors-doc/ajp/printer/ajpv13ext.html Mon Aug 17
10:48:16 2015
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connector - AJP Protocol Reference
- AJPv13 extensions Proposal</title><meta name="author" value="Henri
Gomez"><meta name="email" value="hgo...@apache.org"><link
href="../../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../../images/tomcat.gif"
align="left" alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--RIGHT SIDE MAIN BODY--><td
width="80%" valign="top" align="left"><table border="0" width="100
%" cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connector - AJP Protocol Reference</h1><h2>AJPv13 extensions
Proposal</h2></td><td align="right" valign="top" nowrap="true"><img
src="../../images/void.gif" width="1" height="1" vspace="0" hspace="0"
border="0" alt=" "></td></tr></table><table border="0" cellspacing="0"
cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font color="#ffffff"
face="arial,helvetica.sanserif"><a
name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - AJP Protocol
Reference - AJPv13 extensions Proposal</title><meta name="author" value="Henri
Gomez"><meta name="email" value="hgo...@apache.org"><link
href="../../style.css" type="text/css" rel="stylesheet"></head><body
bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76"
vlink="#525D76"><table border="0" width="100%" cellspacing="4"><!--PAGE
HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../../images/tomcat.gif"
align="left" alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--RIGHT SIDE MAIN BODY--><td
width="80%" valign="top" align="left"><table border="0" width="10
0%" cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connectors - AJP Protocol Reference</h1><h2>AJPv13 extensions
Proposal</h2></td><td align="right" valign="top" nowrap="true"><img
src="../../images/void.gif" width="1" height="1" vspace="0" hspace="0"
border="0" alt=" "></td></tr></table><table border="0" cellspacing="0"
cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font color="#ffffff"
face="arial,helvetica.sanserif"><a
name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
<p>
This document is a proposal of evolution of the current
Apache JServ Protocol version 1.3, also known as ajp13.
@@ -133,7 +133,7 @@ run-time (up/down), level of SSL env var
level supported (level1/level2/level3...)
The Web server info will contain web server info and
-connector name (ie Apache 1.3.26 + mod_ssl 2.8.8 + mod_jk 1.2.1 + mod_perl
1.25).
+connector name (ie Apache 1.3.26 + mod_ssl 2.8.8 + mod_jk 1.2.41 + mod_perl
1.25).
The servlet engine will mask the negociation mask with it's own
mask (what it can do) and return it when loggin is accepted.
@@ -649,5 +649,5 @@ All others flags must be set to 0 since
</blockquote></td></tr></table>
</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
- Copyright © 1999-2014, Apache Software Foundation
+ Copyright © 1999-2015, Apache Software Foundation
</em></font></div></td></tr></table></body></html>
\ No newline at end of file
Added: tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html?rev=1696233&view=auto
==============================================================================
--- tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html
(added)
+++ tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html Mon
Aug 17 10:48:16 2015
@@ -0,0 +1,207 @@
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - Common HowTo -
LoadBalancer HowTo</title><meta name="author" value="Mladen Turk"><meta
name="email" value="mt...@apache.org"><link href="../style.css" type="text/css"
rel="stylesheet"></head><body bgcolor="#ffffff" text="#000000" link="#525D76"
alink="#525D76" vlink="#525D76"><table border="0" width="100%"
cellspacing="4"><!--PAGE HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../images/tomcat.gif" align="left"
alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--LEFT SIDE NAVIGATION--><td
width="20%" valign="top" nowrap="true"><p><strong>Links</strong></p><ul><li><a
href="../in
dex.html">Docs Home</a></li></ul><p><strong>Common
HowTo</strong></p><ul><li><a href="../common_howto/quick.html">For the
impatient</a></li><li><a href="../common_howto/workers.html">All about
workers</a></li><li><a
href="../common_howto/timeouts.html">Timeouts</a></li><li><a
href="../common_howto/loadbalancers.html">Load Balancing</a></li><li><a
href="../common_howto/proxy.html">Reverse
Proxy</a></li></ul><p><strong>Webserver HowTo</strong></p><ul><li><a
href="../webserver_howto/apache.html">Apache HTTP Server</a></li><li><a
href="../webserver_howto/iis.html">IIS</a></li><li><a
href="../webserver_howto/nes.html">Netscape/SunOne/Sun</a></li></ul><p><strong>Reference
Guide</strong></p><ul><li><a
href="../reference/workers.html">workers.properties</a></li><li><a
href="../reference/uriworkermap.html">uriworkermap.properties</a></li><li><a
href="../reference/status.html">Status Worker</a></li><li><a
href="../reference/apache.html">Apache HTTP Server</a></li><li><a
href="../reference/iis
.html">IIS</a></li></ul><p><strong>AJP Protocol
Reference</strong></p><ul><li><a
href="../ajp/ajpv13a.html">AJPv13</a></li><li><a
href="../ajp/ajpv13ext.html">AJPv13 Extension
Proposal</a></li></ul><p><strong>Miscellaneous
Documentation</strong></p><ul><li><a
href="../miscellaneous/faq.html">Frequently asked questions</a></li><li><a
href="../miscellaneous/changelog.html">Changelog</a></li><li><a
href="http://issues.apache.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Tomcat+Connectors&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=No
w&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">Current
Tomcat Connectors bugs</a></li><li><a
href="../miscellaneous/doccontrib.html">Contribute documentation</a></li><li><a
href="../miscellaneous/jkstatustasks.html">JK Status Ant Tasks</a></li><li><a
href="../miscellaneous/reporttools.html">Reporting Tools</a></li><li><a
href="http://tomcat.apache.org/connectors-doc-archive/jk2/index.html";>Old
JK/JK2 documentation</a></li></ul><p><strong>News</strong></p><ul><li><a
href="../news/20140201.html">2014</a></li><li><a
href="../news/20120301.html">2012</a></li><li><a
href="../news/20110701.html">2011</a></li><li><a
href="../news/20100101.html">2010</a></li><li><a
href="../news/20090301.html">2009</a></li><li><a
href="../news/20081001.html">2008</a></li><li><a
href="../news/20070301.html">2007</a></li><li><a
href="../news/20060101.html">2006</a></li><li><a
href="../news/20050101.html">2005</a></li><li><a h
ref="../news/20041100.html">2004</a></li></ul></td><!--RIGHT SIDE MAIN
BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"><tr><td align="left" valign="top"><h1>The Apache Tomcat
Connectors - Common HowTo</h1><h2>LoadBalancer HowTo</h2></td><td align="right"
valign="top" nowrap="true"><small><a href="printer/loadbalancers.html"><img
src="../images/printer.gif" border="0" alt="Printer Friendly
Version"><br>print-friendly<br>version
+ </a></small></td></tr></table><table border="0"
cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
color="#ffffff" face="arial,helvetica.sanserif"><a
name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
+<br>
+<p>A load balancer is a worker that does not directly communicate with Tomcat.
+Instead it is responsible for the management of several "real" workers,
+called members or sub workers of the load balancer.</p>
+<p>
+This management includes:
+</p>
+<ul>
+<li>
+Instantiating the workers in the web server.
+</li>
+<li>
+Using the worker's load-balancing factor, perform weighted load balancing
+(distributing load according to defined strengths of the targets).
+</li>
+<li>
+Keeping requests belonging to the same session executing on the same Tomcat
+(session stickyness).
+</li>
+<li>
+Identifying failed Tomcat workers, suspending requests to them and instead
+falling-back on other workers managed by the load balancer.
+</li>
+<li>
+Providing status and load metrics for the load balancer itself and all
+members via the status worker interface.
+</li>
+<li>
+Allowing to dynamically reconfigure load-balancing via the status worker
+interface.
+</li>
+</ul>
+<p>
+Workers managed by the same load balancer worker are load-balanced
+(based on their configured balancing factors and current request or session
load)
+and also secured against failure by providing failover to other members of the
same
+load balancer. So a single Tomcat process death will not "kill" the entire
site.
+</p>
+<p>Some of the features provided by a load balancer are even interesting, when
+only working with a single member worker (where load balancing is not
possible).</p>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Basic Load Balancer Properties"><strong>Basic Load Balancer
Properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>A worker is configured as a load balancer by setting its worker <b
class="code">type</b>
+to <b>lb</b>.
+</p>
+<p>
+The following table specifies some properties used to configure a load
balancer worker:
+</p>
+<ul>
+<li><b>balance_workers</b> is a comma separated list of names of the member
workers of the
+load balancer. These workers are typically of type <b>ajp13</b>. The member
workers do
+not need to appear in the <b class="code">worker.list</b> property themselves,
adding the
+load balancer to it suffices.</li>
+<li><b>sticky_session</b> specifies whether requests with SESSION ID's should
be routed
+back to the same Tomcat instance that created the session. You can set
sticky_session to
+<b>false</b> when Tomcat is using a session manager which can share session
data across
+multiple instances of Tomcat - or if your application is stateless.
+By default sticky_session is set to <b>true</b>.</li>
+<li><b>lbfactor</b> can be added to each member worker to configure individual
+strengths for the members. A higher <b class="code">lbfactor</b> will lead to
more
+requests being balanced to that worker. The factors must be given by integers
and the
+load will be distributed proportional to the factors given. Higher factors
lead to
+more requests.</li>
+</ul>
+
+<div class="example"><pre>
+ # The load balancer worker balance1 will distribute
+ # load to the members worker1 and worker2
+ worker.balance1.type=lb
+ worker.balance1.balance_workers=worker1, worker2
+ worker.worker1.type=ajp13
+ worker.worker1.host=myhost1
+ worker.worker1.port=8009
+ worker.worker2.type=ajp13
+ worker.worker1.host=myhost2
+ worker.worker1.port=8009
+</pre></div>
+
+<p><font color="#ff0000">
+Session stickyness is not implemented using a tracking table for sessions.
+Instead each Tomcat instance gets an individual name and adds its name at
+the end of the session id. When the load balancer sees a session id, it
+finds the name of the Tomcat instance and sends the request via the correct
+member worker. For this to work you must set the name of the Tomcat instances
+as the value of the <b class="code">jvmRoute</b> attribute in the Engine
element of
+each Tomcat's server.xml. The name of the Tomcat needs to be equal to the name
+of the corresponding load balancer member. In the above example, Tomcat on host
+"myhost1" needs <b class="code">jvmRoute="worker1"</b>, Tomcat on host
"myhost2"
+needs <b class="code">jvmRoute="worker2"</b>.
+</font></p>
+
+<p>For a complete reference of all load balancer configuration
+attributes, please consult the worker <a
href="../reference/workers.html">reference</a>.
+</p>
+</blockquote></td></tr></table>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Advanced Load Balancer Worker Properties"><strong>Advanced Load Balancer
Worker Properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>The load balancer supports complex topologies and failover configurations.
+Using the member attribute <b class="code">distance</b> you can group members.
+The load balancer will always send a request to a member of lowest distance.
+Only when all of those are broken, it will balance to the members of the
+next higher configured distance. This allows to define priorities between
+Tomcat instances in different data center locations.
+</p>
+<p>When working with shared sessions, either by using session replication
+or a persisting session manager (e.g. via a database), one often splits
+up the Tomcat farm into replication groups. In case of failure of a member,
+the load balancer needs to know, which other members share the session.
+This is configured using the <b class="code">domain</b> attribute. All workers
+with the same domain are assumed to share the sessions.</p>
+<p>For maintenance purposes you can tell the load balancer to not
+allow any new sessions on some members, or even not use them at all.
+This is controlled by the member attribute <b class="code">activation</b>.
+The value <b>Active</b> allows normal use of a member, <b>disabled</b>
+will not create new sessions on it, but still allow sticky requests,
+and <b>stopped</b> will no longer send any requests to the member.
+Switching the activation from "active" to "disabled" some time before
+maintenance will drain the sessions on the worker and minimize disruption.
+Depending on the usage pattern of the application, draining will take from
+minutes to hours. Switching the worker to stopped immediately before
+maintenance will reduce logging of false errors by mod_jk.</p>
+<p>Finally you can also configure hot spare workers by using
+<b class="code">activation</b> set to <b>disabled</b> in combination with
+the attribute <b class="code">redirect</b> added to the other workers:</p>
+
+<div class="example"><pre>
+ # The advanced router LB worker
+ worker.list=router
+ worker.router.type=lb
+ worker.router.balance_workers=worker1,worker2
+
+ # Define the first member worker
+ worker.worker1.type=ajp13
+ worker.worker1.host=myhost1
+ worker.worker1.port=8009
+ # Define preferred failover node for worker1
+ worker.worker1.redirect=worker2
+
+ # Define the second member worker
+ worker.worker2.type=ajp13
+ worker.worker2.host=myhost2
+ worker.worker2.port=8009
+ # Disable worker2 for all requests except failover
+ worker.worker2.activation=disabled
+</pre></div>
+
+<p>
+The <b class="code">redirect</b> flag on worker1 tells the load balancer
+to redirect the requests to worker2 in case that worker1 has a problem.
+In all other cases worker2 will not receive any requests, thus acting
+like a hot standby.
+</p>
+
+<p>A final note about setting <b class="code">activation</b> to
<b>disabled</b>:
+The session id coming with a request is send either
+as part of the request URL (<b class="code">;jsessionid=...</b>) or via a
cookie.
+When using bookmarks or browsers that are running since a long time,
+it is possible to send a request carrying an old and invalid session id
+pointing at a disabled member.
+Since the load balancer does not have a list of valid sessions, it will
+forward the request to the disabled member. Thus draining takes longer than
+expected. To handle such cases, you can add a Servlet filter to your web
+application, which checks the request attribute <b
class="code">JK_LB_ACTIVATION</b>.
+This attribute contains one of the strings "ACT", "DIS" or "STP". If you
+detect "DIS" and the session for the request is no longer active, delete the
+session cookie and redirect using a self-referential URL. The redirected
+request will then no longer carry session information and thus the load
+balancer will not send it to the disabled worker. The request attribute
+<b class="code">JK_LB_ACTIVATION</b> has been added in version 1.2.32.</p>
+</blockquote></td></tr></table>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Status Worker properties"><strong>Status Worker
properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>
+The status worker does not communicate with Tomcat.
+Instead it is responsible for the worker management. It is
+especially useful when combined with load balancer workers.
+</p>
+<div class="example"><pre>
+ # Add the status worker to the worker list
+ worker.list=jkstatus
+ # Define a 'jkstatus' worker using status
+ worker.jkstatus.type=status
+</pre></div>
+<p>Next thing is to mount the requests to the jkstatus worker. For Apache
+web servers use the:</p>
+<div class="example"><pre>
+ # Add the jkstatus mount point
+ JkMount /jkmanager/* jkstatus
+</pre></div>
+<p>To obtain a higher level of security use the:</p>
+<div class="example"><pre>
+ # Enable the JK manager access from localhost only
+ <Location /jkmanager/>
+ JkMount jkstatus
+ Order deny,allow
+ Deny from all
+ Allow from 127.0.0.1
+ </Location>
+</pre></div>
+
+</blockquote></td></tr></table>
+
+</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
+ Copyright © 1999-2015, Apache Software Foundation
+ </em></font></div></td></tr></table></body></html>
\ No newline at end of file
Propchange:
tomcat/site/trunk/docs/connectors-doc/common_howto/loadbalancers.html
------------------------------------------------------------------------------
svn:eol-style = native
Added:
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html?rev=1696233&view=auto
==============================================================================
---
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html
(added)
+++
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html
Mon Aug 17 10:48:16 2015
@@ -0,0 +1,206 @@
+<html><head><META http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>The Apache Tomcat Connectors - Common HowTo -
LoadBalancer HowTo</title><meta name="author" value="Mladen Turk"><meta
name="email" value="mt...@apache.org"><link href="../../style.css"
type="text/css" rel="stylesheet"></head><body bgcolor="#ffffff" text="#000000"
link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%"
cellspacing="4"><!--PAGE HEADER--><tr><td colspan="2"><!--TOMCAT LOGO--><a
href="http://tomcat.apache.org/";><img src="../../images/tomcat.gif"
align="left" alt="Apache Tomcat" border="0"></a><!--APACHE LOGO--><a
href="http://www.apache.org/";><img
src="http://www.apache.org/images/asf-logo.gif"; align="right" alt=" :: Apache
Software Foundation" border="0"></a></td></tr><!--HEADER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><tr><!--RIGHT SIDE MAIN BODY--><td
width="80%" valign="top" align="left"><table border="0" width="100%"
cellspacing="4"
><tr><td align="left" valign="top"><h1>The Apache Tomcat Connectors - Common
>HowTo</h1><h2>LoadBalancer HowTo</h2></td><td align="right" valign="top"
>nowrap="true"><img src="../../images/void.gif" width="1" height="1"
>vspace="0" hspace="0" border="0" alt=" "></td></tr></table><table border="0"
>cellspacing="0" cellpadding="2" width="100%"><tr><td bgcolor="#525D76"><font
>color="#ffffff" face="arial,helvetica.sanserif"><a
>name="Introduction"><strong>Introduction</strong></a></font></td></tr><tr><td><blockquote>
>
+<br>
+<p>A load balancer is a worker that does not directly communicate with Tomcat.
+Instead it is responsible for the management of several "real" workers,
+called members or sub workers of the load balancer.</p>
+<p>
+This management includes:
+</p>
+<ul>
+<li>
+Instantiating the workers in the web server.
+</li>
+<li>
+Using the worker's load-balancing factor, perform weighted load balancing
+(distributing load according to defined strengths of the targets).
+</li>
+<li>
+Keeping requests belonging to the same session executing on the same Tomcat
+(session stickyness).
+</li>
+<li>
+Identifying failed Tomcat workers, suspending requests to them and instead
+falling-back on other workers managed by the load balancer.
+</li>
+<li>
+Providing status and load metrics for the load balancer itself and all
+members via the status worker interface.
+</li>
+<li>
+Allowing to dynamically reconfigure load-balancing via the status worker
+interface.
+</li>
+</ul>
+<p>
+Workers managed by the same load balancer worker are load-balanced
+(based on their configured balancing factors and current request or session
load)
+and also secured against failure by providing failover to other members of the
same
+load balancer. So a single Tomcat process death will not "kill" the entire
site.
+</p>
+<p>Some of the features provided by a load balancer are even interesting, when
+only working with a single member worker (where load balancing is not
possible).</p>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Basic Load Balancer Properties"><strong>Basic Load Balancer
Properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>A worker is configured as a load balancer by setting its worker <b
class="code">type</b>
+to <b>lb</b>.
+</p>
+<p>
+The following table specifies some properties used to configure a load
balancer worker:
+</p>
+<ul>
+<li><b>balance_workers</b> is a comma separated list of names of the member
workers of the
+load balancer. These workers are typically of type <b>ajp13</b>. The member
workers do
+not need to appear in the <b class="code">worker.list</b> property themselves,
adding the
+load balancer to it suffices.</li>
+<li><b>sticky_session</b> specifies whether requests with SESSION ID's should
be routed
+back to the same Tomcat instance that created the session. You can set
sticky_session to
+<b>false</b> when Tomcat is using a session manager which can share session
data across
+multiple instances of Tomcat - or if your application is stateless.
+By default sticky_session is set to <b>true</b>.</li>
+<li><b>lbfactor</b> can be added to each member worker to configure individual
+strengths for the members. A higher <b class="code">lbfactor</b> will lead to
more
+requests being balanced to that worker. The factors must be given by integers
and the
+load will be distributed proportional to the factors given. Higher factors
lead to
+more requests.</li>
+</ul>
+
+<div class="example"><pre>
+ # The load balancer worker balance1 will distribute
+ # load to the members worker1 and worker2
+ worker.balance1.type=lb
+ worker.balance1.balance_workers=worker1, worker2
+ worker.worker1.type=ajp13
+ worker.worker1.host=myhost1
+ worker.worker1.port=8009
+ worker.worker2.type=ajp13
+ worker.worker1.host=myhost2
+ worker.worker1.port=8009
+</pre></div>
+
+<p><font color="#ff0000">
+Session stickyness is not implemented using a tracking table for sessions.
+Instead each Tomcat instance gets an individual name and adds its name at
+the end of the session id. When the load balancer sees a session id, it
+finds the name of the Tomcat instance and sends the request via the correct
+member worker. For this to work you must set the name of the Tomcat instances
+as the value of the <b class="code">jvmRoute</b> attribute in the Engine
element of
+each Tomcat's server.xml. The name of the Tomcat needs to be equal to the name
+of the corresponding load balancer member. In the above example, Tomcat on host
+"myhost1" needs <b class="code">jvmRoute="worker1"</b>, Tomcat on host
"myhost2"
+needs <b class="code">jvmRoute="worker2"</b>.
+</font></p>
+
+<p>For a complete reference of all load balancer configuration
+attributes, please consult the worker <a
href="../../reference/workers.html">reference</a>.
+</p>
+</blockquote></td></tr></table>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Advanced Load Balancer Worker Properties"><strong>Advanced Load Balancer
Worker Properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>The load balancer supports complex topologies and failover configurations.
+Using the member attribute <b class="code">distance</b> you can group members.
+The load balancer will always send a request to a member of lowest distance.
+Only when all of those are broken, it will balance to the members of the
+next higher configured distance. This allows to define priorities between
+Tomcat instances in different data center locations.
+</p>
+<p>When working with shared sessions, either by using session replication
+or a persisting session manager (e.g. via a database), one often splits
+up the Tomcat farm into replication groups. In case of failure of a member,
+the load balancer needs to know, which other members share the session.
+This is configured using the <b class="code">domain</b> attribute. All workers
+with the same domain are assumed to share the sessions.</p>
+<p>For maintenance purposes you can tell the load balancer to not
+allow any new sessions on some members, or even not use them at all.
+This is controlled by the member attribute <b class="code">activation</b>.
+The value <b>Active</b> allows normal use of a member, <b>disabled</b>
+will not create new sessions on it, but still allow sticky requests,
+and <b>stopped</b> will no longer send any requests to the member.
+Switching the activation from "active" to "disabled" some time before
+maintenance will drain the sessions on the worker and minimize disruption.
+Depending on the usage pattern of the application, draining will take from
+minutes to hours. Switching the worker to stopped immediately before
+maintenance will reduce logging of false errors by mod_jk.</p>
+<p>Finally you can also configure hot spare workers by using
+<b class="code">activation</b> set to <b>disabled</b> in combination with
+the attribute <b class="code">redirect</b> added to the other workers:</p>
+
+<div class="example"><pre>
+ # The advanced router LB worker
+ worker.list=router
+ worker.router.type=lb
+ worker.router.balance_workers=worker1,worker2
+
+ # Define the first member worker
+ worker.worker1.type=ajp13
+ worker.worker1.host=myhost1
+ worker.worker1.port=8009
+ # Define preferred failover node for worker1
+ worker.worker1.redirect=worker2
+
+ # Define the second member worker
+ worker.worker2.type=ajp13
+ worker.worker2.host=myhost2
+ worker.worker2.port=8009
+ # Disable worker2 for all requests except failover
+ worker.worker2.activation=disabled
+</pre></div>
+
+<p>
+The <b class="code">redirect</b> flag on worker1 tells the load balancer
+to redirect the requests to worker2 in case that worker1 has a problem.
+In all other cases worker2 will not receive any requests, thus acting
+like a hot standby.
+</p>
+
+<p>A final note about setting <b class="code">activation</b> to
<b>disabled</b>:
+The session id coming with a request is send either
+as part of the request URL (<b class="code">;jsessionid=...</b>) or via a
cookie.
+When using bookmarks or browsers that are running since a long time,
+it is possible to send a request carrying an old and invalid session id
+pointing at a disabled member.
+Since the load balancer does not have a list of valid sessions, it will
+forward the request to the disabled member. Thus draining takes longer than
+expected. To handle such cases, you can add a Servlet filter to your web
+application, which checks the request attribute <b
class="code">JK_LB_ACTIVATION</b>.
+This attribute contains one of the strings "ACT", "DIS" or "STP". If you
+detect "DIS" and the session for the request is no longer active, delete the
+session cookie and redirect using a self-referential URL. The redirected
+request will then no longer carry session information and thus the load
+balancer will not send it to the disabled worker. The request attribute
+<b class="code">JK_LB_ACTIVATION</b> has been added in version 1.2.32.</p>
+</blockquote></td></tr></table>
+
+<table border="0" cellspacing="0" cellpadding="2" width="100%"><tr><td
bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a
name="Status Worker properties"><strong>Status Worker
properties</strong></a></font></td></tr><tr><td><blockquote>
+<p>
+The status worker does not communicate with Tomcat.
+Instead it is responsible for the worker management. It is
+especially useful when combined with load balancer workers.
+</p>
+<div class="example"><pre>
+ # Add the status worker to the worker list
+ worker.list=jkstatus
+ # Define a 'jkstatus' worker using status
+ worker.jkstatus.type=status
+</pre></div>
+<p>Next thing is to mount the requests to the jkstatus worker. For Apache
+web servers use the:</p>
+<div class="example"><pre>
+ # Add the jkstatus mount point
+ JkMount /jkmanager/* jkstatus
+</pre></div>
+<p>To obtain a higher level of security use the:</p>
+<div class="example"><pre>
+ # Enable the JK manager access from localhost only
+ <Location /jkmanager/>
+ JkMount jkstatus
+ Order deny,allow
+ Deny from all
+ Allow from 127.0.0.1
+ </Location>
+</pre></div>
+
+</blockquote></td></tr></table>
+
+</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td
colspan="2"><hr noshade size="1"></td></tr><!--PAGE FOOTER--><tr><td
colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
+ Copyright © 1999-2015, Apache Software Foundation
+ </em></font></div></td></tr></table></body></html>
\ No newline at end of file
Propchange:
tomcat/site/trunk/docs/connectors-doc/common_howto/printer/loadbalancers.html
------------------------------------------------------------------------------
svn:eol-style = native
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
![http://www.apache.org/images/asf-logo.gif"](http://www.apache.org/images/asf-logo.gif"){kind=link}