Low keepalive_requests Value

Gixy Check ID: low_keepalive_requests

The keepalive_requests directive sets the maximum number of requests that can be served through one keep-alive connection. After the maximum number of requests are made, the connection is closed.

Why this matters

Prior to nginx 1.19.10, the default value was 100. This was raised to 1000 because low values can cause problems:

• HTTP/2 multiplexing: Modern browsers open fewer connections but send many requests over each one. A low keepalive_requests value forces frequent connection resets.
• Client disconnections: Some clients (especially when using HTTP/2 with proxies like Burp or mitmproxy) may experience failed requests when connections are closed prematurely.
• Performance overhead: Establishing new connections has overhead (TCP handshake, TLS negotiation). Keeping connections alive longer improves performance.

Bad example

keepalive_requests 100;

This forces connection closure after only 100 requests, which can cause issues with HTTP/2 clients.

Good example

keepalive_requests 1000;

Or simply omit the directive to use nginx's default (1000 since nginx 1.19.10).

References

• nginx documentation: keepalive_requests
• nginx ticket #2155: Increase default keepalive_requests

Harden NGINX with maintained RPMs

Use NGINX Extras by GetPageSpeed for continuously updated NGINX and modules on RHEL/CentOS/Alma/Rocky. Learn more.