WEB SERVERS


Specifying network time-outs on the Web server
Open, inactive sessions can prevent users from accessing the server. Specify time limits for activities between the IBM® Lotus® Domino® Web server and clients or CGI programs so connections do not remain open if there is no network activity between them.

To specify network time-outs on the Web server

1. Open the Server document you want to edit and click Edit Server.

2. Click Internet Protocols - HTTP. In the Timeouts section, complete these fields:
FieldAction
HTTP persistent connectionSpecify whether you want to enable persistent HTTP connections on the Web server. These connections remain active under the following conditions:
  • HTTP protocol is 1.1.
  • The server application returns an HTTP response code less than 400. (If the server application returns an HTTP response code greater than or equal to 400, the connection will be closed by the server.)
  • The HTTP request did come through a proxy server.
  • The client did not send a connection close header.
  • The number of connections that the server can support is running low, or the number of connections queued for the thread processing the request is too large.
If the connection is kept open, then the following settings apply:
  • The connection will be closed if the maximum number of requests per connection is exceeded.
  • The connection will be closed if the persistent time-out is exceeded.
  • The connection will be closed if no data is received by the server within the specified input timeout.
  • The connection will be closed if a complete request is not received within the specified request timeout.
Note Persistent connections require more server overhead than connections that are limited by network activity.
Maximum requests per persistent connectionSpecify the maximum number of HTTP requests that can be handled on one persistent connection. The default is 5.
Persistent connection timeoutSpecify the length of time for which you want persistent connections to remain active. The default is 180 seconds.
Request timeoutSpecify the amount of time for the server to wait to receive an entire request. The default is 60 seconds. If the server doesn't receive the entire request in the specified time interval, the server terminates the connection.
Input timeoutEnter the time, in seconds, that a client has to send a request after connecting to the server. The default is 15 seconds. If no request is sent in the specified time interval, then the server terminates the connection. If only a partial request is sent, the input timer is reset to the specified time limit in anticipation of the rest of the data arriving.
Output timeoutEnter the maximum time, in seconds, that the server has to send output to a client. The default is 180 seconds.
CGI timeoutThe maximum time, in seconds, that a CGI program started by the server has to finish. The default is 180 seconds.
Related topics