iTP Secure WebServer System Administrators Guide (Version 7.5+)

persistent connections for Java clients. The KeepAliveHeader directive can occur only once in
the configuration file.
Default
KeepAliveHeader OFF
The default value is set for all client connections.
Example
KeepAliveHeader ON
KeepAliveTimeout
Syntax
KeepAliveTimeout timeout-value
Description
Use the KeepAliveTimeout directive to specify the number of seconds that the iTP Secure
WebServer should wait for a request before terminating a persistent TCP/IP connection. The
KeepAliveTimeout directive can occur only once in the configuration file.
Persistent connections are a feature introduced in the HTTP/1.1 protocol to improve performance.
In earlier versions of HTTP, each request for a URL resulted in a new connection. Serving a page
often requires many requests (for example to include a graphics file in a page of text), so a complex
page could take considerable time to load. When a server supports persistent connections, it
establishes a connection when the user makes a request; the connection stays open for the series
of related requests the client makes of the server.
This directive enables you to control how long the server waits for the next request from the client.
If the timeout expires, the server closes the connection. If a new request arrives from the client, the
server creates a new connection. The user does not experience any disruption of service.
The timeout-value has a range from 0 seconds to the value of the InputTimeout directive. A
value of 0 causes the server not to create persistent connections; that is, the server will behave as
in previous releases.
Default
KeepAliveTimeout 15
Example
KeepAliveTimeout 30
KeepAliveMaxRequest
Syntax
KeepAliveMaxRequest integer-value
Description
Use the KeepAliveMaxRequest directive to specify the number of requests the iTP Secure
WebServer should handle before closing a persistent connection.
Persistent connections are a feature introduced in the HTTP/1.1 protocol to improve performance.
In earlier versions of HTTP, each request for a URL resulted in a new connection. Serving a page
often requires many requests (for example to include a graphics file in a page of text), so a complex
page could take considerable time to load. When a server supports persistent connections, it
establishes a connection when the user makes a request; the connection stays open for the series
of related requests the client makes of the server.
216 Configuration Directives