1. NGINX Control API: View In-Memory Configuration and Reload via HTTP Requests

    NGINX Blog 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…

  2. Image: NGINX Blog

    NGINX Routing on HTTP Request Body

    NGINX Blog 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…

  3. HTTP Strict Transport Security Policy in NGINX Ingress Controller

    NGINX Blog NGINX Ingress Controller 5.6.0 introduces HSTS as a Policy type for the VirtualServer CRD. This blog gives a quick overview of the feature with some deployment examples and tips on how to correctly configure this policy. Across this blog, we’re focused on: What is HSTS? HTTP…

  4. Predicate Routing for Native Handling of API Traffic

    NGINX Blog 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…

  5. NGINX 1.31.5: Control API, predicate locations, early body inspection, and more

    NGINX Blog 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…

  6. NGINX 1.31.4: PROXY Protocol v2, Stricter Validation and More

    NGINX Blog NGINX 1.31.4 is an incremental release focused on the protocols we all depend on. Backends behind a stream or mail proxy can now see a client’s TLS details alongside its address thanks to PROXY protocol v2, HTTP/2 and gRPC requests to your upstreams follow the standards more…