https://blog.nginx.org/blog/nginx-oss-1-29-6-and-1-29-7-open-sourced-session-persistence-multipath-tcp-and-more NGINX Community Blog NGINX Community Blog * All Posts * GitHub + github.com/nginxinc + github.com/nginx * Forum NGINX OSS 1.29.6 and 1.29.7: Open Sourced Session Persistence, Multipath TCP and More Mar 26, 2026 -- by Michael Vernik in Uncategorized [Screenshot-2025-12-10-at-5] NGINX 1.29.6 and 1.29.7 introduce significant updates and mark the first in a planned series to add capabilities to NGINX Open Source formerly limited to NGINX Plus. With updates to core runtime behavior and network support, these releases ensure that NGINX can continue to meet the needs of modern applications and AI workloads. Highlights of these releases include: * Open sourced sticky cookie session persistence * Upstream proxy connections now default to HTTP/1.1 and no longer require explicitly configured keep-alives and connection headers * Multipath TCP (MPTCP) support * Several important security-related fixes Together, these changes expand what operators can do with NGINX Open Source while simplifying configurations for optimizing performance to proxied services. Open Sourced Sticky Cookies for Session Persistence NGINX 1.29.6 adds support for cookie-based session persistence to open source, a capability previously only available commercially in NGINX Plus. Sticky cookies allow NGINX to issue a session cookie and route subsequent requests from that client to the same upstream server. Unlike IP-based affinity methods, cookie persistence avoids issues introduced by NAT, mobile networks, carrier-grade proxies, or large-scale edge routing. Example configuration: upstream backend { server backend1.example.com; server backend2.example.com; sticky cookie srv_id expires=1h domain=.example.com path=/; } Why it matters: * Many production workloads still rely on in-memory session state * Stateless design is not always immediately achievable * Cookie-based persistence provides deterministic routing without requiring external session stores or application refactoring Who it helps: * E-commerce platforms maintaining transactional continuity * Real-time dashboards and WebSocket applications * Enterprises modernizing legacy stateful services * Platform teams that need controlled session affinity in Kubernetes or VM environments Default to HTTP/1.1 for Upstream Connections NGINX 1.29.7 now defaults to HTTP/1.1 when proxying to upstreams. HTTP/1.1 enables persistent upstream connections via keep-alives, chunked transfer encoding, and broader compatibility with modern application frameworks. Learn more about this change in our dedicated post on this topic. Why it matters: * Operators no longer need to explicitly configure HTTP/ 1.1, enable keep-alives and remove connection headers when routing traffic to upstreams * Backend interoperability issues are reduced * Default behavior aligns with modern framework expectations Who it helps: * Teams running modern frameworks that expect persistent connections * Operators troubleshooting inconsistent upstream behavior * Platform teams standardizing proxy behavior across environments Multipath TCP (MPTCP) Support NGINX 1.29.7 adds support for Multipath TCP (MPTCP). MPTCP allows a single TCP connection to use multiple network paths simultaneously, improving resilience and throughput in multi-homed or heterogeneous network environments. Why it matters: * Applications benefit from improved reliability without modification * Transport-layer resilience increases as kernel-level MPTCP support matures * Infrastructure performance improves across heterogeneous networks Who it helps: * Edge and mobile deployments with variable connectivity * Multi-interface servers in high-availability configurations * Infrastructure teams optimizing network resilience A Deliberate Direction NGINX 1.29.6 and 1.29.7 represent our continued effort to align NGINX Open Source more closely with modern application requirements. Over the next several months, we will continue to release more commercial features as open source and, while subject to change, we have made these and other plans public in our new Github roadmap. Capabilities made available in NGINX 1.29.6 and 1.29.7, along with several bug and security fixes, mean that NGINX Open Source is now even more performant and production-ready. We encourage you to upgrade to NGINX 1.29.7 to take advantage of all the new features and ensure that you're protected by all the latest security patches. View all updates and fixes in GitHub: 1.29.6 -> https://github.com/nginx/nginx/releases/tag/release-1.29.6 1.29.7 -> https://github.com/nginx/nginx/releases/tag/release-1.29.7 Download NGINX and view the full changelog. NGINX Community Forum announcement release --------------------------------------------------------------------- -Previous: Keep-alive to upstreams is now default in NGINX 1.29.7 [NGINX-Part-of-F5-horiz-black-type-300x119] Search [ ] GitHub nginxinc nginx Other Sites Community Forum NGINX.org F5.com Social * + YouTube * + Bluesky * + X (c) 2025 F5, Inc. | All Rights Reserved Manage Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional [ ] Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences [ ] Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics [ ] Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing [ ] Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. * Manage options * Manage services * Manage {vendor_count} vendors * Read more about these purposes Accept Deny View preferences Save preferences View preferences * {title} * {title} * {title} Manage consent