Did You Know Nginx Now Enables HTTP/1.1 Keep‑Alive by Default?

For a long time many developers assumed Nginx enabled keep‑alive automatically, especially as newer releases focus on HTTP/3 and have already stabilized HTTP/2. The reality is that, until recently, using HTTP/1.1 required explicit directives in the configuration:

proxy_http_version 1.1;
proxy_set_header Connection "";

These lines forced Nginx to speak HTTP/1.1 and to send an empty Connection header, thereby activating keep‑alive. In current mainline versions this configuration has become the default, so the directives are no longer necessary.

Enabling HTTP/1.1 keep‑alive brings two main benefits: it reduces the number of TCP handshakes and cuts latency, which in turn shortens the time to first byte (TTFB) for most conventional web applications.

Reviewing existing projects, the author found that many still contain the explicit HTTP/1.1 keep‑alive settings, while some sections surprisingly omit them, highlighting a lingering inconsistency in configuration practices.

The piece also reflects on the broader industry context: while AI and new concepts like Harness Engineering dominate headlines, many production systems still run on Java 8 with layered dependencies and have not adopted HTTP/2, coexisting with the hype‑driven demos on the same servers.