Connection Pool Management settings. Please refer to Apache HttpComponents Connection Management Connection Pool Management setting: max total concurrent connections that will be created by a connection pool manager Connection Pool Management setting: max total concurrent connections for a route that will be created by a connection pool manager. Defines the socket timeout (SO_TIMEOUT) in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. This parameter expects a value of type java.lang.Integer. If this parameter is not set, read operations will not time out (infinite timeout). Determines the size of the internal socket buffer used to buffer data while receiving / transmitting HTTP messages. Determines the timeout in milliseconds until a connection is established. A timeout value of zero is interpreted as an infinite timeout. If this parameter is not set, connect operations will not time out (infinite timeout). Determines the maximum line length limit. If set to a positive value, any HTTP line exceeding this limit will cause an java.io.IOException. A zero value will effectively disable the check and no limit will be enforced. Determines the maximum HTTP header count allowed. If set to a positive value, the number of HTTP headers received from the data stream exceeding this limit will cause an java.io.IOException. A zero value will effectively disable the check and no limit will be enforced. Defines the maximum number of ignorable lines before we expect a HTTP response's status line. With HTTP/1.1 persistent connections, the problem arises that broken scripts could return a wrong Content-Length (there are more bytes sent than specified). Unfortunately, in some cases, this cannot be detected after the bad response, but only before the next one. So HttpClient must be able to skip those surplus lines this way. 0 disallows all garbage/empty lines before the status line. Use java.lang.Integer#MAX_VALUE for unlimited number. Determines whether Nagle's algorithm is to be used. Nagle's algorithm tries to conserve bandwidth by minimizing the number of segments that are sent. When applications wish to decrease network latency and increase performance, they can disable Nagle's algorithm (that is enable TCP_NODELAY. Data will be sent earlier, at the cost of an increase in bandwidth consumption. If this parameter is not set, TCP_NODELAY will be enabled (no delay). Some HTTP servers use a non-standard Keep-Alive header to communicate to the client the period of time in seconds they intend to keep the connection alive on the server side. If this header is present in the response, the value in this header will be used to determine the maximum length of time to keep a persistent connection open for. If the Keep-Alive header is NOT present in the response, the value of keepalive.timeout is evaluated. If this value is 0, the connection will be kept alive indefinitely. If the value is greater than 0, the connection will be kept alive for the number of milliseconds specified. Please refer to Apache HttpComponents Connection Management Unique pool identifier. Determines whether or not this pool configuration should be considered the default when a pool of HTTP connections is requested from the service. Determines whether or not this client should send chunked data when forwarding requests to the origin service. If set to true or 1, chunked data will always be sent. Using the value 1 is considered deprecated and will be removed in the next major release. If set to false or 0, chunked data will never be sent. Using the value 0 is considered deprecated and will be removed in the next major release. If set to auto, chunked data will only be sent if the original request to Repose was chunked. Note that the auto setting only has meaning for the default connection pool, as that is the only pool that will be used to make requests to the origin service. WARNING: Setting this attribute to false may cause repose to attempt to retrieve the actual content length through reading the ServletInputStream. This will cause some performance degradation as request body is no longer always streamed through. IF this attribute is configured, THEN it is assumed that it points to the Java keystore containing the client certificate to present for client authentication (e.g keystore.jks) AND the keystore-password and key-password attributes are no longer optional. The password for the client authentication keystore. The password for the particular client authentication key in the keystore. The truststore used for validating the server this pool is connecting to. This is typically set to the same path as the client authentication keystore. The password for the client authentication truststore. NOTE: This element is only used if the truststore-filename attribute is present. List of headers to add to each request made using this connection pool. Header with a name and a value.