iTP Secure WebServer System Administrators Guide (Version 7.5+)

This directive enables you to control how many requests the server will accept on the same
connection. If the number is exceeded, the server closes the connection; when the next request
arrives, the server creates a new connection. The user does not experience any disruption of service.
The integer-value has a range from -1 to 32767. A value less than -1 or greater than 32767
results in an error message.
Values from 0 to 32767 indicate the number of requests that the Webserver will service on the
same persistent connection before closing the connection. A value of 0 or 1 disables persistent
conditions. A value of -1 indicates that the Webserver will keep the persistent connection open
until the client closes the connection or the Webserver encounters an error while processing the
request.
Default
KeepAliveMaxRequest 255
Example
KeepAliveMaxRequest 50
KeyDatabase
Syntax
KeyDatabase key-database-filename
Description
Use the KeyDatabase directive to specify the name of the database file that contains the relevant
certificate and private keys for server authentication.
Consider the following when you configure iTP Secure WebServer for client authentication:
• If ClientCADatabase directive is configured, the iTP Secure WebServer reads the trusted
client root certificates from the specified database file. The database file specified with
KeyDatabase directive must have only the relevant private and public keys, and certificates
for server authentication.
• If ClientCADatabase directive is not configured, the iTP Secure WebServer reads the trusted
client root certificates from the database file specified with KeyDatabase directive. The
database file specified with KeyDatabase directive must have the relevant public and private
keys, certificates for server authentication, trusted client root certificates and other certificates
for client authentication.
Only one KeyDatabase directive is allowed in the configuration file. If there are multiple entries
in the configuration file, the last entry is used.
NOTE: HP recommends the following:
• Configure KeyDatabase for server certificates, and private and public key pairs
• Configure ClientCADatabase for client certificates
If you configure KeyDatabase for both, the following are also sent to the client as trusted root
certificates:
• CA root of server certificate chain
• Intermediate certificate of server certificate chain
Default
None. This is a mandatory directive for secure communication.
Example
KeyDatabase $root/conf/keys
KeyDatabase 217