Chapter 10: HTTP Connectors . disableUploadTimeout: This attribute
Chapter 10: HTTP Connectors . disableUploadTimeout: This attribute enables a separate timeout to be set (or not set) for data uploads during a servlet execution. The attribute s value defaults to false. . emptySessionPath: Default is false. The session path used for cookies is all / if set to true. In general, set this to true only when the server is used to run applications written to the Port- lets specification. . enableLookups: When this is set to true, all calls to request.getRemoteHost()perform a DNS lookup to return the host name for the remote client. When this attribute is false, the DNS lookup is skipped and only the IP address is returned. The default value for enableLookupsis false. Keeping this attribute turned off increases performance, which enables you to avoid the overhead required for the DNS lookup. These and other performance considerations are discussed in the section Performance Tuning, later in this chapter. . maxHttpHeaderSize: This attribute controls the maximum size of the request and response headers. The unit is bytes. The default value is 4096 (4K). . maxKeepAliveRequest: This attribute controls the keep-alive behavior of HTTP requests that enables persistent connections (that is, multiple requests to be sent over the same HTTP connection). It specifies the maximum number of requests that can be pipelined until the connection is closed by the server. The default value of maxKeepAliveRequestis 100, and setting it to 1disables HTTP keep-alive behavior and pipelining. . maxPostSize: This specifies the maximum size, in bytes, of the POSTthat can be handled by the container. It defaults to 2,097,152 (2MB). If set to 0 or a negative number, this feature is disabled. . maxSavePostSize: This specifies the maximum size, in bytes, of the POSTthat can be handled by the container during a client-cert or form authentication operation. It defaults to 4096 (4K). If set to -1, this feature is disabled and POSTed data is not saved during the two types of authentication. . maxSpareThreads: The maxSpareThreads attribute controls the maximum number of unused threads that are allowed to exist before Tomcat starts stopping the unused ones. maxSpareThreadsdefaults to 50. . minSpareThreads: The minSpareThreads attribute specifies the minimum number of threads that are started when the Connector is initialized. minSpareThreadsdefaults to 4. . maxThreads: This attribute specifies the maximum number of threads that are created for this Connector to process requests. This, in turn, specifies the maximum number of concurrent requests that the Connector can handle. maxThreads defaults to 200 threads. . noCompressionUserAgents: This is a comma-separated list that matches the HTTP UserAgent value of Web browsers that have a broken support for HTTP/1.1 compression. Regular expressions can be used here. . port: The port attribute specifies the TCP port number on which this Connector will create a server socket and await incoming connections. Only one server application can bind to a particular port number IP address combination. . protocol: This specifies the HTTP protocol to use, and must be set to HTTP/1.1(the default). This loads the default org.apache.coyote.http11.Http11Protocol. . implementation: This is the default Java-based blocking connector. If you specify org .apache.coyote.http11.Http11NioProtocol, the non-blocking NIO connector is selected. If you specify org.apache.coyote.http11.Http11AprProtocol, the APR connector is
For reliable and cheap web hosting services please check cheap web hosting website.