The number of thread dedicated to accepting incoming connections.
Number of connection requests that can be queued up before the operating system starts to send rejections.
Sets the priority of the acceptor threads relative to the other threads.
The port to redirect to if there is a security constraint of CONFIDENTIAL.
https by default
Set the size of the buffer to be used for request and response headers. An idle connection will at most have one buffer of this size allocated. Default is 4K.
The particular interface to listen on. If not set or 0.0.0.0, jetty will listen on port on all interfaces.
The port to redirect to if there is a security constraint of INTEGRAL.
Set the number of connections, which if exceeded places this connector in a low resources state. This is not an exact measure as the connection count is averaged over the select sets. When in a low resources state, different idle timeouts can apply on connections (see lowResourcesMaxIdleTime).
Set the period in ms that a connection is allowed to be idle when this there are more than lowResourcesConnections connections. This allows the server to rapidly close idle connections in order to gracefully handle high load situations.
Set the maximum Idle time for a connection, which roughly translates to the Socket.setSoTimeout(int) call, although with NIO implementations other mechanisms may be used to implement the timeout. The max idle time is applied: when waiting for a new request to be received on a connection; when reading the headers and content of a request; when writing the headers and content of a response. Jetty interprets this value as the maximum time between some progress being made on the connection. So if a single byte is read or written, then the timeout (if implemented by jetty) is reset. However, in many instances, the reading/writing is delegated to the JVM, and the semantic is more strictly enforced as the maximum time a single read/write operation can take. Note, that as Jetty supports writes of memory mapped file buffers, then a write may take many 10s of seconds for large content written to a slow device.
The name of the connector. Can be used to make a WebAppContext respond only to requests on the named connector via the [WebAppContext.setConnectorNames(String)http://jetty.mortbay.org/jetty-6/apidocs/org/mortbay/jetty/webapp/WebAppContext.html] method
The port to listen on. See also host
Set the size of the content buffer for receiving requests. These buffers are only used for active connections that have requests with bodies that will not fit within the header buffer (see headerBufferSize). Default is 8K.
Set the size of the content buffer for sending responses. These buffers are only used for active connections that are sending responses with bodies that will not fit within the header buffer. Default is 32K.
If true, request IP addresses will be resolved to host names
True if the the server socket will be opened in SO_REUSEADDR mode
Sets SO_LINGER on the connection socket. Disabled by default.
If true, enables statistics collection on connections see Statistics
For nio connectors, determines whether direct byte buffers will be used or not. The default is true.