The number of milliseconds this Connector will wait, after accepting a connection, for the request URI line to be
presented. Use a value of -1 to indicate no (i.e. infinite) timeout. The default value is 60000 (i.e. 60 seconds) but note
that the standard server.xml that ships with Tomcat sets this to 20000 (i.e. 20 seconds). Unless disableUploadTimeout is
set to false, this timeout will also be used when reading the request body (if any).
If this Connector is supporting non-SSL requests, and a request is received for which a matching <security-constraint>
requires SSL transport, Catalina will automatically redirect the request to the port number specified here.
The minimum number of threads always kept running. If not specified, the default of 10 is used.
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.
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.
Set to true if you want calls to request.getRemoteHost() to perform DNS lookups in order to return the actual host name of
the remote client. Set to false to skip the DNS lookup and return the IP address in String form instead (thereby improving
performance). By default, DNS lookups are disabled.
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.
The percentage of processing threads that have to be in use before HTTP keep-alives are disabled to improve scalability.
Values less than 0 will be changed to 0 and values greater than 100 will be changed to 100. If not specified, the default
value is 75.
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 acceptCount setting. The default value varies by connector type. For BIO the default is the value
of maxThreads unless an Executor is used in which case the default will be the value of maxThreads from the executor. For
NIO the default is 10000. For APR/native, the default is 8192.
Note that for APR/native on Windows, the configured value will be reduced to the highest multiple of 1024 that is less than
or equal to maxConnections. This is done for performance reasons.
If set to a value of -1, the maxConnections feature is disabled and connections are not counted.
The number of milliseconds this Connector will wait for another HTTP request before closing the connection. The default
value is to use the value that has been set for the connectionTimeout attribute. Use a value of -1 to indicate no (i.e.
The value is a comma separated list of MIME types for which HTTP compression may be used. The default value is
The Connector may use HTTP/1.1 GZIP compression in an attempt to save server bandwidth. The acceptable values for the
parameter is “off” (disable compression), “on” (allow compression, which causes text data to be compressed), “force”
(forces compression in all cases), or a numerical integer value (which is equivalent to “on”, but specifies the minimum
amount of data before the output is compressed). If the content-length is not known and compression is set to “on” or more
aggressive, the output will also be compressed. If not specified, this attribute is set to “off”.
Note: There is a tradeoff between using compression (saving your bandwidth) and using the sendfile feature (saving your CPU
cycles). If the connector supports the sendfile feature, e.g. the NIO connector, using sendfile will take precedence over
compression. The symptoms will be that static files greater that 48 Kb will be sent uncompressed. You can turn off sendfile
by setting useSendfile attribute of the connector, as documented below, or change the sendfile usage threshold in the
configuration of the DefaultServlet in the default conf/web.xml or in the web.xml of your web application.
If compression is set to “on” then this attribute may be used to specify the minimum amount of data before the output is
compressed. If not specified, this attribute is defaults to “2048”.
org.apache.coyote.http11.Http11Protocol – blocking Java connector
org.apache.coyote.http11.Http11NioProtocol – non blocking Java connector
org.apache.coyote.http11.Http11AprProtocol – the APR/native connector.