Parameter:
HTTPMaxRequestsPerPersistentConnectionShort description: Limits the number of HTTP requests per keep-alive connection before it is closed.
Profile
Parameter | HTTPMaxRequestsPerPersistentConnection |
Category | HTTP / Web |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Server document (Internet Protocols → HTTP) |
Possible values | Integer (default 100; typical values 50–500) |
Description
Domino keeps HTTP connections open with
Keep-Alive so that subsequent requests can be served without a new TCP/TLS handshake. HTTPMaxRequestsPerPersistentConnection defines the upper bound per connection – after that, the socket is closed, which frees memory and relieves load balancers from long-lived connections.Example configuration
HTTPMaxRequestsPerPersistentConnection=200
Notes & pitfalls
- Value
0= unlimited – not recommended.
- The default of
100is enough in most cases; for API / REST loads,200–500can make sense.
- Pairs with
HTTPKeepAliveTimeoutandHTTPMaxConnections.
- With an upstream reverse proxy, this is usually limited on the proxy side as well.
- The change takes effect after a restart of the HTTP task.