Gecko [ edgpens.lpkmn.gov.my ]

Name	Size	Permission
ajp.html	53.52 KB	-rw-rw-rw-
automatic-deployment.html	78.04 KB	-rw-rw-rw-
cluster-channel.html	12.05 KB	-rw-rw-rw-
cluster-deployer.html	10.31 KB	-rw-rw-rw-
cluster-interceptor.html	32.31 KB	-rw-rw-rw-
cluster-listener.html	8.6 KB	-rw-rw-rw-
cluster-manager.html	26.82 KB	-rw-rw-rw-
cluster-membership.html	14.12 KB	-rw-rw-rw-
cluster-receiver.html	16.68 KB	-rw-rw-rw-
cluster-sender.html	18 KB	-rw-rw-rw-
cluster-valve.html	16.63 KB	-rw-rw-rw-
cluster.html	16.29 KB	-rw-rw-rw-
context.html	96.03 KB	-rw-rw-rw-
engine.html	18.48 KB	-rw-rw-rw-
executor.html	11.98 KB	-rw-rw-rw-
filter.html	114.75 KB	-rw-rw-rw-
globalresources.html	18.98 KB	-rw-rw-rw-
host.html	41.36 KB	-rw-rw-rw-
http.html	95.74 KB	-rw-rw-rw-
index.html	8.73 KB	-rw-rw-rw-
jar-scanner.html	11.84 KB	-rw-rw-rw-
listeners.html	45.44 KB	-rw-rw-rw-
loader.html	15.9 KB	-rw-rw-rw-
manager.html	39.54 KB	-rw-rw-rw-
realm.html	75.08 KB	-rw-rw-rw-
resources.html	12.17 KB	-rw-rw-rw-
server.html	10.82 KB	-rw-rw-rw-
service.html	9.92 KB	-rw-rw-rw-
sessionidgenerator.html	10.85 KB	-rw-rw-rw-
systemprops.html	50.22 KB	-rw-rw-rw-
valve.html	129.69 KB	-rw-rw-rw-

Code Editor : ajp.html

<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 7 Configuration Reference (7.0.107) - The AJP Connector</title><meta name="author" content="Remy Maucherat"><meta name="author" content="Yoav Shapira"><meta name="author" content="Andrew R. Jaquith"><style type="text/css" media="print">
 .noPrint {display: none;}
 td#mainBody {width: 100%;}
</style><style type="text/css">
code {background-color:rgb(224,255,255);padding:0 0.1em;}
code.attributeName, code.propertyName {background-color:transparent;}

table {
 border-collapse: collapse;
 text-align: left;
}
table *:not(table) {
 /* Prevent border-collapsing for table child elements like <div> */
 border-collapse: separate;
}

th {
  text-align: left;
}

div.codeBox pre code, code.attributeName, code.propertyName, code.noHighlight, .noHighlight code {
 background-color: transparent;
}
div.codeBox {
 overflow: auto;
 margin: 1em 0;
}
div.codeBox pre {
 margin: 0;
 padding: 4px;
 border: 1px solid #999;
 border-radius: 5px;
 background-color: #eff8ff;
 display: table; /* To prevent <pre>s from taking the complete available width. */
 /*
 When it is officially supported, use the following CSS instead of display: table
 to prevent big <pre>s from exceeding the browser window:
 max-width: available;
 width: min-content;
 */
}

div.codeBox pre.wrap {
  white-space: pre-wrap;
}

table.defaultTable tr, table.detail-table tr {
    border: 1px solid #CCC;
}

table.defaultTable tr:nth-child(even), table.detail-table tr:nth-child(even) {
    background-color: #FAFBFF;
}

table.defaultTable tr:nth-child(odd), table.detail-table tr:nth-child(odd) {
    background-color: #EEEFFF;
}

table.defaultTable th, table.detail-table th {
  background-color: #88b;
  color: #fff;
}

table.defaultTable th, table.defaultTable td, table.detail-table th, table.detail-table td {
  padding: 5px 8px;
}

p.notice {
 border: 1px solid rgb(255, 0, 0);
 background-color: rgb(238, 238, 238);
 color: rgb(0, 51, 102);
 padding: 0.5em;
 margin: 1em 2em 1em 1em;
}
</style></head><body bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%" cellspacing="0"><tr><td><a href="https://tomcat.apache.org/"><img src="../images/tomcat.gif" align="right" alt="
 The Apache Tomcat Servlet/JSP Container
 " border="0"></a></td><td><h1>Apache Tomcat 7</h1>Version 7.0.107, Nov 18 2020</td><td><a href="http://www.apache.org/"><img src="../images/asf-logo.svg" align="right" alt="Apache Logo" border="0" style="width: 266px;height: 83px;"></a></td></tr></table><table border="0" width="100%" cellspacing="4"><tr><td colspan="2"><hr noshade size="1"></td></tr><tr><td width="20%" valign="top" nowrap class="noPrint">Links<ul><li><a href="../index.html">Docs Home</a></li><li><a href="index.html">Config Ref. Home</a></li><li><a href="https://wiki.apache.org/tomcat/FAQ">FAQ</a></li><li><a href="#comments_section">User Comments</a></li></ul>Top Level Elements<ul><li><a href="server.html">Server</a></li><li><a href="service.html">Service</a></li></ul>Executors<ul><li><a href="executor.html">Executor</a></li></ul>Connectors<ul><li><a href="http.html">HTTP</a></li><li><a href="ajp.html">AJP</a></li></ul>Containers<ul><li><a href="context.html">Context</a></li><li><a href="engine.html">Engine</a></li><li><a href="host.html">Host</a></li><li><a href="cluster.html">Cluster</a></li></ul>Nested Components<ul><li><a href="globalresources.html">Global Resources</a></li><li><a href="jar-scanner.html">JarScanner</a></li><li><a href="listeners.html">Listeners</a></li><li><a href="loader.html">Loader</a></li><li><a href="manager.html">Manager</a></li><li><a href="realm.html">Realm</a></li><li><a href="resources.html">Resources</a></li><li><a href="sessionidgenerator.html">SessionIdGenerator</a></li><li><a href="valve.html">Valve</a></li></ul>Cluster Elements<ul><li><a href="cluster.html">Cluster</a></li><li><a href="cluster-manager.html">Manager</a></li><li><a href="cluster-channel.html">Channel</a></li><li><a href="cluster-membership.html">Channel/Membership</a></li><li><a href="cluster-sender.html">Channel/Sender</a></li><li><a href="cluster-receiver.html">Channel/Receiver</a></li><li><a href="cluster-interceptor.html">Channel/Interceptor</a></li><li><a href="cluster-valve.html">Valve</a></li><li><a href="cluster-deployer.html">Deployer</a></li><li><a href="cluster-listener.html">ClusterListener</a></li></ul>web.xml<ul><li><a href="filter.html">Filter</a></li></ul>Other<ul><li><a href="systemprops.html">System properties</a></li></ul></td><td width="80%" valign="top" align="left" id="mainBody"><h1>The AJP Connector</h1><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Table of Contents"></a><a name="Table_of_Contents">Table of Contents</a></td></tr><tr><td><blockquote>
<ul><li><a href="#Introduction">Introduction</a></li><li><a href="#Attributes">Attributes</a><ol><li><a href="#Common_Attributes">Common Attributes</a></li><li><a href="#Standard_Implementations">Standard Implementations</a></li><li><a href="#Java_TCP_socket_attributes">Java TCP socket attributes</a></li><li><a href="#NIO_specific_configuration">NIO specific configuration</a></li><li><a href="#APR/native_specific_configuration">APR/native specific configuration</a></li></ol></li><li><a href="#Nested_Components">Nested Components</a></li><li><a href="#Special_Features">Special Features</a><ol><li><a href="#Proxy_Support">Proxy Support</a></li><li><a href="#Connector_Comparison">Connector Comparison</a></li></ol></li></ul>
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Introduction">Introduction</a></td></tr><tr><td><blockquote>

The AJP Connector element represents a
 Connector component that communicates with a web
 connector via the <code>AJP</code> protocol. This is used for cases
 where you wish to invisibly integrate Tomcat into an existing (or new)
 Apache installation, and you want Apache to handle the static content
 contained in the web application, and/or utilize Apache's SSL
 processing.

This connector supports load balancing when used in conjunction with
 the <code>jvmRoute</code> attribute of the
 <a href="engine.html">Engine</a>.

The native connectors supported with this Tomcat release are:
 <ul>
 <li>JK 1.2.x with any of the supported servers. See
 <a href="https://tomcat.apache.org/connectors-doc/">the JK docs</a>
 for details.</li>
 <li>mod_proxy on Apache httpd 2.x (included by default in Apache HTTP
 Server 2.2), with AJP enabled: see
 <a href="https://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html">the
 httpd docs</a> for details.</li>
 </ul>

Other native connectors supporting AJP may work, but are no longer
 supported.

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Attributes">Attributes</a></td></tr><tr><td><blockquote>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Common Attributes"></a><a name="Common_Attributes">Common Attributes</a></td></tr><tr><td><blockquote>

All implementations of Connector
 support the following attributes:

<table border="1" cellpadding="5"><tr><th width="15%" bgcolor="#023264">Attribute</th><th width="85%" bgcolor="#023264">Description</th></tr><tr><td align="left" valign="center"><code class="attributeName">ajpFlush</code></td><td align="left" valign="center">
 A boolean value which can be used to enable or disable sending
 AJP flush messages to the fronting proxy whenever an explicit
 flush happens. The default value is <code>true</code>. 
 An AJP flush message is a SEND_BODY_CHUNK packet with no body content.
 Proxy implementations like mod_jk or mod_proxy_ajp will flush the
 data buffered in the web server to the client when they receive
 such a packet. Setting this to <code>false</code> can reduce
 AJP packet traffic but might delay sending packets to the client.
 At the end of the response, AJP does always flush to the client.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">allowTrace</code></td><td align="left" valign="center">
 A boolean value which can be used to enable or disable the TRACE
 HTTP method. If not specified, this attribute is set to false.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">asyncTimeout</code></td><td align="left" valign="center">
 The default timeout for asynchronous requests in milliseconds. If not
 specified, this attribute is set to 10000 (10 seconds).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">enableLookups</code></td><td align="left" valign="center">
 Set to <code>true</code> if you want calls to
 <code>request.getRemoteHost()</code> to perform DNS lookups in
 order to return the actual host name of the remote client. Set
 to <code>false</code> to skip the DNS lookup and return the IP
 address in String form instead (thereby improving performance).
 By default, DNS lookups are disabled.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">encodedSolidusHandling</code></td><td align="left" valign="center">
 When set to <code>reject</code> request paths containing a
 <code>%2f</code> sequence will be rejected with a 400 response. When set
 to <code>decode</code> request paths containing a <code>%2f</code>
 sequence will have that sequence decoded to <code>/</code> at the same
 time other <code>%nn</code> sequences are decoded. When set to
 <code>passthrough</code> request paths containing a <code>%2f</code>
 sequence will be processed with the <code>%2f</code> sequence unchanged.
 If not specified the default value is <code>reject</code>. This default
 may be modified if the deprecated <a href="systemprops.html">system
 property</a>
 <code>org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH</code> is
 set.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxHeaderCount</code></td><td align="left" valign="center">
 The maximum number of headers in a request that are allowed by the
 container. A request that contains more headers than the specified limit
 will be rejected. A value of less than 0 means no limit.
 If not specified, a default of 100 is used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxParameterCount</code></td><td align="left" valign="center">
 The maximum number of parameter and value pairs (GET plus POST) which
 will be automatically parsed by the container. Parameter and value pairs
 beyond this limit will be ignored. A value of less than 0 means no limit.
 If not specified, a default of 10000 is used. Note that
 <code>FailedRequestFilter</code> <a href="filter.html">filter</a> can be
 used to reject requests that hit the limit.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxPostSize</code></td><td align="left" valign="center">
 The maximum size in bytes of the POST which will be handled by
 the container FORM URL parameter parsing. The limit can be disabled by
 setting this attribute to a value less than zero. If not specified, this
 attribute is set to 2097152 (2 megabytes). Note that the
 <a href="filter.html#Failed_Request_Filter"><code>FailedRequestFilter</code></a>
 can be used to reject requests that exceed this limit.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxSavePostSize</code></td><td align="left" valign="center">
 The maximum size in bytes of the POST which will be saved/buffered by
 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
 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).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">parseBodyMethods</code></td><td align="left" valign="center">
 A comma-separated list of HTTP methods for which request
 bodies using <code>application/x-www-form-urlencoded</code> will be parsed
 for request parameters identically to POST. This is useful in RESTful
 applications that want to support POST-style semantics for PUT requests.
 Note that any setting other than <code>POST</code> causes Tomcat
 to behave in a way that goes against the intent of the servlet
 specification.
 The HTTP method TRACE is specifically forbidden here in accordance
 with the HTTP specification.
 The default is <code>POST</code>
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">port</code></td><td align="left" valign="center">
 The TCP port number on which this Connector
 will create a server socket and await incoming connections. Your
 operating system will allow only one server application to listen
 to a particular port number on a particular IP address. If the special
 value of 0 (zero) is used, then Tomcat will select a free port at random
 to use for this connector. This is typically only useful in embedded and
 testing applications.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">protocol</code></td><td align="left" valign="center">
 Sets the protocol to handle incoming traffic. To configure an AJP
 connector this must be specified. If no value for protocol is provided,
 an <a href="http.html">HTTP connector</a> rather than an AJP connector
 will be configured. 
 The standard protocol value for an AJP connector is <code>AJP/1.3</code>
 which uses an auto-switching mechanism to select either a Java based
 connector or an APR/native based connector. If the
 <code>PATH</code> (Windows) or <code>LD_LIBRARY_PATH</code> (on most unix
 systems) environment variables contain the Tomcat native library, the
 native/APR connector will be used. If the native library cannot be
 found, the Java BIO based connector will be used. 
 To use an explicit protocol rather than rely on the auto-switching
 mechanism described above, the following values may be used: 
 <code>org.apache.coyote.ajp.AjpProtocol</code>
 - blocking Java connector 
 <code>org.apache.coyote.ajp.AjpNioProtocol</code>
 - non blocking Java connector. 
 <code>org.apache.coyote.ajp.AjpAprProtocol</code>
 - the APR/native connector. 
 Custom implementations may also be used. 
 Take a look at our <a href="#Connector_Comparison">Connector
 Comparison</a> chart.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">proxyName</code></td><td align="left" valign="center">
 If this Connector is being used in a proxy
 configuration, configure this attribute to specify the server name
 to be returned for calls to <code>request.getServerName()</code>.
 See <a href="#Proxy_Support">Proxy Support</a> for more
 information.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">proxyPort</code></td><td align="left" valign="center">
 If this Connector is being used in a proxy
 configuration, configure this attribute to specify the server port
 to be returned for calls to <code>request.getServerPort()</code>.
 See <a href="#Proxy_Support">Proxy Support</a> for more
 information.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">redirectPort</code></td><td align="left" valign="center">
 If this Connector is supporting non-SSL
 requests, and a request is received for which a matching
 <code>&lt;security-constraint&gt;</code> requires SSL transport,
 Catalina will automatically redirect the request to the port
 number specified here.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">scheme</code></td><td align="left" valign="center">
 Set this attribute to the name of the protocol you wish to have
 returned by calls to <code>request.getScheme()</code>. For
 example, you would set this attribute to "<code>https</code>"
 for an SSL Connector. The default value is "<code>http</code>".
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secure</code></td><td align="left" valign="center">
 Set this attribute to <code>true</code> if you wish to have
 calls to <code>request.isSecure()</code> to return <code>true</code>
 for requests received by this Connector. You would want this on an
 SSL Connector or a non SSL connector that is receiving data from a
 SSL accelerator, like a crypto card, an SSL appliance or even a webserver.
 The default value is <code>false</code>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">URIEncoding</code></td><td align="left" valign="center">
 This specifies the character encoding used to decode the URI bytes,
 after %xx decoding the URL. If not specified, ISO-8859-1 will be used.
 
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">useBodyEncodingForURI</code></td><td align="left" valign="center">
 This specifies if the encoding specified in contentType should be used
 for URI query parameters, instead of using the URIEncoding. This
 setting is present for compatibility with Tomcat 4.1.x, where the
 encoding specified in the contentType, or explicitly set using
 Request.setCharacterEncoding method was also used for the parameters from
 the URL. The default value is <code>false</code>.
 
 Notes: See notes on this attribute in
 <a href="http.html">HTTP Connector</a> documentation.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">useIPVHosts</code></td><td align="left" valign="center">
 Set this attribute to <code>true</code> to cause Tomcat to use
 the IP address passed by the native web server to determine the Host
 to send the request to. The default value is <code>false</code>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">xpoweredBy</code></td><td align="left" valign="center">
 Set this attribute to <code>true</code> to cause Tomcat to advertise
 support for the Servlet specification using the header recommended in the
 specification. The default value is <code>false</code>.
 </td></tr></table>

</blockquote></td></tr></table>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Standard Implementations"></a><a name="Standard_Implementations">Standard Implementations</a></td></tr><tr><td><blockquote>

To use AJP, you must specify the protocol attribute (see above).

The standard AJP connectors (BIO, NIO and APR/native) all support the
 following attributes in addition to the common Connector attributes listed
 above.

<table border="1" cellpadding="5"><tr><th width="15%" bgcolor="#023264">Attribute</th><th width="85%" bgcolor="#023264">Description</th></tr><tr><td align="left" valign="center"><code class="attributeName">acceptCount</code></td><td align="left" valign="center">
 The maximum queue length for incoming connection requests when
 all possible request processing threads are in use. Any requests
 received when the queue is full will be refused. The default
 value is 100.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">acceptorThreadCount</code></td><td align="left" valign="center">
 The number of threads to be used to accept connections. Increase this
 value on a multi CPU machine, although you would never really need more
 than <code>2</code>. Also, with a lot of non keep alive connections, you
 might want to increase this value as well. Default value is
 <code>1</code>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">acceptorThreadPriority</code></td><td align="left" valign="center">
 The priority of the acceptor threads. The threads used to accept
 new connections. The default value is <code>5</code> (the value of the
 <code>java.lang.Thread.NORM_PRIORITY</code> constant). See the JavaDoc
 for the <code>java.lang.Thread</code> class for more details on what
 this priority means.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">address</code></td><td align="left" valign="center">
 For servers with more than one IP address, this attribute specifies
 which address will be used for listening on the specified port. By
 default, the connector will listen on the loopback address. Unless the JVM
 is configured otherwise using system properties, the Java based connectors
 (BIO, NIO) will listen on both IPv4 and IPv6 addresses when configured
 with either <code>0.0.0.0</code> or <code>::</code>. The APR/native
 connector will only listen on IPv4 addresses if configured with
 <code>0.0.0.0</code> and will listen on IPv6 addresses and the equivalent
 IPv4 address if present when configured with <code>::</code>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">allowedRequestAttributesPattern</code></td><td align="left" valign="center">
 The AJP protocol passes some information from the reverse proxy to the
 AJP connector using request attributes. These attributes are:
 <ul>
 <li>javax.servlet.request.cipher_suite</li>
 <li>javax.servlet.request.key_size</li>
 <li>javax.servlet.request.ssl_session</li>
 <li>javax.servlet.request.X509Certificate</li>
 <li>AJP_LOCAL_ADDR</li>
 <li>AJP_REMOTE_PORT</li>
 <li>AJP_SSL_PROTOCOL</li>
 <li>JK_LB_ACTIVATION</li>
 <li>CERT_ISSUER (IIS only)</li>
 <li>CERT_SUBJECT (IIS only)</li>
 <li>CERT_COOKIE (IIS only)</li>
 <li>HTTPS_SERVER_SUBJECT (IIS only)</li>
 <li>CERT_FLAGS (IIS only)</li>
 <li>HTTPS_SECRETKEYSIZE (IIS only)</li>
 <li>CERT_SERIALNUMBER (IIS only)</li>
 <li>HTTPS_SERVER_ISSUER (IIS only)</li>
 <li>HTTPS_KEYSIZE (IIS only)</li>
 </ul>
 The AJP protocol supports the passing of arbitrary request attributes.
 Requests containing arbitrary request attributes will be rejected with a
 403 response unless the entire attribute name matches this regular
 expression. If not specified, the default value is <code>null</code>.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">bindOnInit</code></td><td align="left" valign="center">
 Controls when the socket used by the connector is bound. By default it
 is bound when the connector is initiated and unbound when the connector is
 destroyed. If set to <code>false</code>, the socket will be bound when the
 connector is started and unbound when it is stopped.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">clientCertProvider</code></td><td align="left" valign="center">
 When client certificate information is presented in a form other than
 instances of <code>java.security.cert.X509Certificate</code> it needs to
 be converted before it can be used and this property controls which JSSE
 provider is used to perform the conversion. For example it is used with
 the AJP connectors, the <a href="http.html">HTTP APR connector</a> and
 with the <a href="valve.html#SSL_Authenticator_Valve">
 org.apache.catalina.valves.SSLValve</a>.If not specified, the default
 provider will be used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">connectionLinger</code></td><td align="left" valign="center">
 The number of seconds during which the sockets used by this
 Connector will linger when they are closed. The default
 value is <code>-1</code> which disables socket linger.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">connectionTimeout</code></td><td align="left" valign="center">
 The number of milliseconds this Connector will wait,
 after accepting a connection, for the request URI line to be
 presented. The default value for AJP protocol connectors
 is <code>-1</code> (i.e. infinite).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">executor</code></td><td align="left" valign="center">
 A reference to the name in an <a href="executor.html">Executor</a>
 element. If this attribute is set, and the named executor exists, the
 connector will use the executor, and all the other thread attributes will
 be ignored. Note that if a shared executor is not specified for a
 connector then the connector will use a private, internal executor to
 provide the thread pool.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">executorTerminationTimeoutMillis</code></td><td align="left" valign="center">
 The time that the private internal executor will wait for request
 processing threads to terminate before continuing with the process of
 stopping the connector. If not set, the default is <code>0</code> (zero)
 for the BIO connector and <code>5000</code> (5 seconds) for the NIO and
 APR/native connectors.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">keepAliveTimeout</code></td><td align="left" valign="center">
 The number of milliseconds this Connector will wait for
 another AJP request before closing the connection.
 The default value is to use the value that has been set for the
 connectionTimeout attribute.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxConnections</code></td><td align="left" valign="center">
 The maximum number of connections that the server will accept and
 process at any given time. When this number has been reached, the server
 will accept, but not process, one further connection. This additional
 connection be blocked until the number of connections being processed
 falls below maxConnections at which point the server will
 start accepting and processing new connections again. Note that once the
 limit has been reached, the operating system may still accept connections
 based on the <code>acceptCount</code> setting. The default value varies by
 connector type. For BIO the default is the value of
 maxThreads unless an <a href="executor.html">Executor</a>
 is used in which case the default will be the value of maxThreads from the
 executor. For NIO the default is <code>10000</code>.
 For APR/native, the default is <code>8192</code>.
 For NIO only, setting the value to -1, will disable the
 maxConnections feature and connections will not be counted.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxCookieCount</code></td><td align="left" valign="center">
 The maximum number of cookies that are permitted for a request. A value
 of less than zero means no limit. If not specified, a default value of 200
 will be used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">maxThreads</code></td><td align="left" valign="center">
 The maximum number of request processing threads to be created
 by this Connector, which therefore determines the
 maximum number of simultaneous requests that can be handled. If
 not specified, this attribute is set to 200. If an executor is associated
 with this connector, this attribute is ignored as the connector will
 execute tasks using the executor rather than an internal thread pool. Note
 that if an executor is configured any value set for this attribute will be
 recorded correctly but it will be reported (e.g. via JMX) as
 <code>-1</code> to make clear that it is not used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">minSpareThreads</code></td><td align="left" valign="center">
 The minimum number of threads always kept running. This includes both
 active and idle threads. If not specified, the default of <code>10</code>
 is used. If an executor is associated with this connector, this attribute
 is ignored as the connector will execute tasks using the executor rather
 than an internal thread pool. Note that if an executor is configured any
 value set for this attribute will be recorded correctly but it will be
 reported (e.g. via JMX) as <code>-1</code> to make clear that it is not
 used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">packetSize</code></td><td align="left" valign="center">
 This attribute sets the maximum AJP packet size in Bytes. The maximum
 value is 65536. It should be the same as the <code>max_packet_size</code>
 directive configured for mod_jk. Normally it is not necessary to change
 the maximum packet size. Problems with the default value have been
 reported when sending certificates or certificate chains. The default
 value is 8192. If set to less than 8192 then the setting will ignored and
 the default value of 8192 used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">processorCache</code></td><td align="left" valign="center">
 The protocol handler caches Processor objects to speed up performance.
 This setting dictates how many of these objects get cached.
 <code>-1</code> means unlimited, default is <code>200</code>. If not using
 Servlet 3.0 asynchronous processing, a good default is to use the same as
 the maxThreads setting. If using Servlet 3.0 asynchronous processing, a
 good default is to use the larger of maxThreads and the maximum number of
 expected concurrent requests (synchronous and asynchronous).
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secret</code></td><td align="left" valign="center">
 Only requests from workers with this secret keyword will be accepted.
 The default value is <code>null</code>. This attribute must be specified
 with a non-null, non-zero length value unless
 secretRequired is explicitly configured to be
 <code>false</code>. If this attribute is configured with a non-null,
 non-zero length value then the workers must provide a
 matching value else the request will be rejected irrespective of the
 setting of secretRequired.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">secretRequired</code></td><td align="left" valign="center">
 If this attribute is <code>true</code>, the AJP Connector will only
 start if the secret attribute is configured with a
 non-null, non-zero length value. This attribute only controls whether
 the secret attribute is required to be specified for the
 AJP Connector to start. It does not control whether
 workers are required to provide the secret. The default value is
 <code>true</code>. This attribute should only be set to <code>false</code>
 when the Connector is used on a trusted network.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">tcpNoDelay</code></td><td align="left" valign="center">
 If set to <code>true</code>, the TCP_NO_DELAY option will be
 set on the server socket, which improves performance under most
 circumstances. This is set to <code>true</code> by default.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">threadPriority</code></td><td align="left" valign="center">
 The priority of the request processing threads within the JVM.
 The default value is <code>5</code> (the value of the
 <code>java.lang.Thread.NORM_PRIORITY</code> constant). See the JavaDoc
 for the <code>java.lang.Thread</code> class for more details on what
 this priority means.If an executor is associated
 with this connector, this attribute is ignored as the connector will
 execute tasks using the executor rather than an internal thread pool. Note
 that if an executor is configured any value set for this attribute will be
 recorded correctly but it will be reported (e.g. via JMX) as
 <code>-1</code> to make clear that it is not used.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">tomcatAuthentication</code></td><td align="left" valign="center">
 If set to <code>true</code>, the authentication will be done in Tomcat.
 Otherwise, the authenticated principal will be propagated from the native
 webserver and used for authorization in Tomcat. 
 The web server must send the user principal (username) as a request
 attribute named <code>REMOTE_USER</code>.
 Note that this principal will have no roles associated with it.
 The default value is <code>true</code>. If
 <code>tomcatAuthorization</code> is set to <code>true</code> this
 attribute has no effect.
 </td></tr><tr><td align="left" valign="center"><code class="attributeName">tomcatAuthorization</code></td><td align="left" valign="center">
 If set to <code>true</code>, the authenticated principal will be
 propagated from the native webserver and considered already authenticated
 in Tomcat. If the web application has one or more security constraints,
 authorization will then be performed by Tomcat and roles assigned to the
 authenticated principal. If the appropriate Tomcat Realm for the request
 does not recognise the provided user name, a Principal will be still be
 created but it will have no roles. The default value is
 <code>false</code>.
 </td></tr></table>

</blockquote></td></tr></table>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Java TCP socket attributes"></a><a name="Java_TCP_socket_attributes">Java TCP socket attributes</a></td></tr><tr><td><blockquote>

The BIO and NIO implementation support the following Java TCP socket
 attributes in addition to the common Connector and HTTP attributes listed
 above.

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="NIO specific configuration"></a><a name="NIO_specific_configuration">NIO specific configuration</a></td></tr><tr><td><blockquote>

The following attributes are specific to the NIO connector.

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="APR/native specific configuration"></a><a name="APR/native_specific_configuration">APR/native specific configuration</a></td></tr><tr><td><blockquote>

The APR/native implementation supports the following attributes in
 addition to the common Connector and AJP attributes listed above.

</blockquote></td></tr></table>

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Nested Components"></a><a name="Nested_Components">Nested Components</a></td></tr><tr><td><blockquote>

None at this time.

</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><a name="Special Features"></a><a name="Special_Features">Special Features</a></td></tr><tr><td><blockquote>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Proxy Support"></a><a name="Proxy_Support">Proxy Support</a></td></tr><tr><td><blockquote>

The <code>proxyName</code> and <code>proxyPort</code> attributes can
 be used when Tomcat is run behind a proxy server. These attributes
 modify the values returned to web applications that call the
 <code>request.getServerName()</code> and <code>request.getServerPort()</code>
 methods, which are often used to construct absolute URLs for redirects.
 Without configuring these attributes, the values returned would reflect
 the server name and port on which the connection from the proxy server
 was received, rather than the server name and port to whom the client
 directed the original request.

For more information, see the
 <a href="../proxy-howto.html">Proxy Support HOW-TO</a>.

</blockquote></td></tr></table>

<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><a name="Connector Comparison"></a><a name="Connector_Comparison">Connector Comparison</a></td></tr><tr><td><blockquote>

Below is a small chart that shows how the connectors differ.
 <div class="codeBox"><pre><code>
 Java Blocking Connector Java Nio Blocking Connector APR/native Connector
 BIO NIO APR
 Classname AjpProtocol AjpNioProtocol AjpAprProtocol
 Tomcat Version 3.x onwards 7.x onwards 5.5.x onwards
 Support Polling NO YES YES
 Polling Size N/A maxConnections maxConnections
 Read Request Headers Blocking Blocking Blocking
 Read Request Body Blocking Blocking Blocking
 Write Response Blocking Blocking Blocking
 Wait for next Request Blocking Non Blocking Non Blocking
 Max Connections maxConnections maxConnections maxConnections

</code></pre></div>

</blockquote></td></tr></table>

</blockquote></td></tr></table></td></tr><tr><td colspan="2"><hr noshade size="1"></td></tr><tr><td colspan="2"><div align="center">
 Copyright &copy; 1999-2020, Apache Software Foundation
 </div></td></tr></table></body></html>

${this.title}

Code Editor : ajp.html