nginx 1.27

NGINX 1.27 continued the mainline branch’s HTTP/3 and QUIC work and delivered incremental HTTP proxying, upstream, and operational improvements. Notable additions included proxy_pass_trailers, which can forward HTTP response trailers from an upstream server when the required HTTP/1.1 trailer handling is configured, and variable support in several upstream response-rate limiting directives. Later 1.27 updates made dynamic DNS resolution and DNS service discovery for upstream servers available in open-source NGINX, allowing eligible upstream names to be re-resolved without a configuration reload. The cycle also accumulated bug fixes across core HTTP, stream, TLS, and QUIC-related code.

NGINX 1.27 has reached end of life, so it will not receive further upstream fixes for security defects, crashes, protocol handling problems, or interoperability regressions. A deployment can remain operational, but any newly discovered issue must be mitigated locally, patched by the operating-system supplier if that supplier backports a fix, or accepted as residual risk. This is especially consequential for internet-facing reverse proxies and for deployments using TLS, HTTP/2, HTTP/3, QUIC, dynamic upstream resolution, or third-party modules. Staying also increases migration cost over time as operating systems, OpenSSL versions, container base images, and module builds move forward independently.

Plan an upgrade to a currently maintained NGINX line and identify whether each installation uses the upstream open-source package, an operating-system package with backported patches, NGINX Plus, or a custom build. Record the exact version, configure arguments, loaded dynamic modules, TLS library, configuration includes, and active HTTP, stream, and QUIC features. Test the target build with production-like traffic and configuration, paying particular attention to TLS negotiation, HTTP/2 and HTTP/3 behavior, proxy trailers where used, DNS-driven upstream membership, cache behavior, rate limits, and logs or metrics consumed by automation. Rebuild or obtain ABI-compatible third-party dynamic modules for the target NGINX build, deploy through a staged rollout with health checks and a tested rollback path, and retire 1.27 instances after the replacement is verified.