Tag: core
-

NGINX 1.31.9: Stricter header parsing, flood detection for chunked request bodies, and protocol fixes for HTTP/2 and HTTP/3
NGINX Open Source 1.31.9 changes how NGINX parses and schedules HTTP traffic. A header line without a colon now fails the request instead of passing through as an empty header, and chunked uploads get flood detection. Several HTTP/2 and HTTP/3 fixes keep traffic moving and headers intact. The rest of the release covers stability. Proxied…
-

NGINX 1.31.8: Working directory validation, portability improvements, and quieter kernel TLS logs
Editor’s note: This release blog should have been published a few weeks ago but slipped through the cracks, so we are publishing it together with the latest release blog! If you set working_directory for core files, NGINX Open Source 1.31.8 catches an invalid path with nginx -t before you deploy. Portability improvements keep HTTP/3, HTTP…
-

NGINX 1.31.7: Native GeoIP2 support, HTTP/2 priorities, and QUIC improvements
Knowing where traffic comes from can help you decide where it goes. NGINX Open Source 1.31.7 brings GeoIP2 and GeoLite2 database support to the existing native GeoIP modules, giving users a straightforward path to current geolocation data. This release also adds modern HTTP/2 prioritization, improves reloads and binary upgrades for BPF-enabled QUIC deployments, and includes…
-

NGINX Control API: View In-Memory Configuration and Reload via HTTP Requests
Before the latest release, NGINX had to be controlled exclusively by Unix signals. The most notable one is SIGHUP or the well-known “nginx -s reload” command. This configuration method, while very stable, does not meet modern environment requirements: there are very few available options, no direct feedback messages on errors, and no real extensibility. We…
-

NGINX Routing on HTTP Request Body
Note: Written by a human. In blog diagram graphic made by AI. NGINX processes HTTP requests in phases. Each phase is designed for specific actions and decisions on the qualities of the request. However, reading of various parts of the request is spread out through multiple phases. A HTTP request consists of several distinct parts.…
-

Predicate Routing for Native Handling of API Traffic
Note: No AI was hurt while writing this blog post. Human tears only. In September 2026 we introduced NGINX 1.31.5 with several core features for one same goal. We expanded the core routing methods and the most critical nginx directives to enable native, non-scripted routing of any API traffic. In this blog post we will…
-

NGINX 1.31.5: Control API, predicate locations, early body inspection, and more
For over two decades, NGINX has been the workhorse of the modern web. Its classic request-processing architecture—reading HTTP headers, matching a URI location path, and streaming payload data to backend services—built the foundation of modern web traffic management. However, the way web applications and AI agent systems communicate is fundamentally evolving. Modern application stacks rely…
